Re: Gerrit 2.5.2 replication does not work with authGroup

515 views
Skip to first unread message

Patrick Renaud

unread,
Mar 11, 2013, 5:22:11 PM3/11/13
to Nicolas Terray, Repo and Gerrit Discussion
Nicolas,

I had a similar issue when I tested this scheme in my test lab a couple of weeks ago. It may seem dumb but make a second change to the project configuration (anything) after giving read rights to group crampons-replication; then a subsequent push to the project will result in a proper replication operation to occur to crampons.cro.enalean.com. At least this is what I observed in my lab although I didn't investigate too deeply after that.

If this works for you too then it may seem to point in the direction of dirty data still cached in memory.


/Patrick


On 11 March 2013 11:39, Nicolas Terray <nicolas...@gmail.com> wrote:
Howdy all,

I am using Gerrit 2.5.2 and I configured the replication as such:

  url = gito...@crampons.cro.enalean.com:${name}.git
  push = +refs/heads/*:refs/heads/*
  push = +refs/tags/*:refs/tags/*
  authGroup = crampons-replication
  replicationDelay = 0

In gerrit web interface the group "crampons-replication" exists, has no member in it and is visible to all registered users. The project has Read permission for this group on refs/*.

When I push something in gerrit, nothing is replicated. The gerrit error_log says nothing.

However, if I remove the authGroup line (and restart gerrit), everything works like a charm.

Could you please help me to make it works? How can I debug and see what is happening (logs are not really verbose)?

Thanks,
Nicolas Terray

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
 
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Nicolas Terray

unread,
Mar 12, 2013, 4:58:36 AM3/12/13
to Patrick Renaud, Repo and Gerrit Discussion
Hi Patrick,

After many changes to the access rights, it works like a charm now.

Thank you very much,
Nicolas

Manuel Vacelet

unread,
Mar 12, 2013, 9:30:22 AM3/12/13
to Nicolas Terray, Patrick Renaud, Repo and Gerrit Discussion
So it confirms there is a bug in gerrit replication.

Shall we fill a bug in to keep track on it ?
--
Twitter: @vaceletm

Manuel Vacelet

unread,
Mar 13, 2013, 1:01:08 PM3/13/13
to Nicolas Terray, Patrick Renaud, Repo and Gerrit Discussion
After a couple of hours of various trial/errors, I cannot find any reliable way to setup the authGroup replication working.
Sometime it happens to work but no way to undersand how and why.

I filled a bug report for that: http://code.google.com/p/gerrit/issues/detail?id=1827

Manuel
--
Twitter: @vaceletm

Steffen Gebert

unread,
Mar 13, 2013, 1:16:35 PM3/13/13
to Repo and Gerrit Discussion
Since the replication plugin the group has to be publicly visible. Is this the case?



Manuel Vacelet <manuel....@gmail.com> schrieb:

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Manuel Vacelet

unread,
Mar 13, 2013, 3:46:27 PM3/13/13
to Steffen Gebert, Repo and Gerrit Discussion
Yes it is.

As said, it works eventually after some modifications of permissions.

Nota: we try to automate this setup so we grant permissions  with modifications of refs/meta/config.
I suspect there is something done on the UI when the Read permission is granted to the replication group and this thing might not be done when we modify directly the configuration with git.

I don't know how to investigate this any further.

Manuel Vacelet

unread,
Mar 14, 2013, 5:03:32 AM3/14/13
to Steffen Gebert, Repo and Gerrit Discussion
Hi,

I made few more tests (still using gerrit 2.5.2):
#1 "cli create-project" + set with refs/meta/config all permissions (including replication "Read = group..."), then commit in repo => No replication
- #1 + "set-project -d foo " => No replication
- #1 + flush-caches --all => No replication
- #1 + server restart => No replication

#2 "cli create-project" + set with refs/meta/config all permissions (without replication group), then commit in the repo, then grant Read right to replication group via refs/meta/config => No replication
- #2 + "set-project -d foo " => No replication
- #2 + flush-caches --all => No replication
- #2 + server restart => No replication

#3 set (direct commit on refs/meta/config) all permissions, grant read access to replication group via Web UI => Replication works!

Is it possible that something is done when using Web UI to make the changes that is not done when modifing refs/meta/config ?

Manuel
--
Twitter: @vaceletm

Manuel Vacelet

unread,
Mar 14, 2013, 10:54:48 AM3/14/13
to Steffen Gebert, Repo and Gerrit Discussion
I made the same tests with gerrit and replication plugins built out of master:
- gerrit 2.5.2-1684-g443a3a1
- replication 1.1-SNAPSHOT (API Version    2.6-SNAPSHOT)

I get the same behaviour: authGroup only works when permission "Read on refs/* to replication group" is manually set from Web UI



--
Twitter: @vaceletm

Manuel Vacelet

unread,
Mar 26, 2013, 8:30:34 PM3/26/13
to Steffen Gebert, dbor...@google.com, Repo and Gerrit Discussion
Hi all,

After quick debugging session together with Dave Borowitz at EclipseCon today, the issue comes from case handeling on permissions.
Replication plugin seems very picky on the case, you have to push "read = group blablabla" for refs/* reference.
We were pushing "Read = group blablabla" and it just doesn't work, even if it's displayed properly on the web UI.

So, for us the fix is easy but I think there is a bug on replication plugin (I started to dig in the sources but it's above my competences).

Manuel
--
Twitter: @vaceletm
Reply all
Reply to author
Forward
0 new messages