Gerrit Pushing to Wrong Branch

[Nicholas Mucci]

Hello,

We've had a couple instances where a user would perform a git push and
their changes would not end up on the branch they specified. For
example:

$ git push origin foo_release:refs/heads/bar-release

would create a Gerrit code review change and then submit to the foobar
branch on the server instead of bar-release, and there would be a
comment indicating the change was pushed to the bar-release branch.

The other case where we saw this involved Gerrit replacing existing
changesets and submitting when a git push was done. A user submitted
two changesets to the foo branch, with change ids 11411 and 11412. He
also uploaded the same two changesets to the bar branch, 11516 and
11517, waiting to be reviewed. When we cherrypick the 11411 and 11412
changes to the quux branch, Gerrit would automatically upload and
replace the 11516 and 11517 changesets, then submit them to the quux
branch.

I'm not sure what is causing this behavior. This is occurring on
Gerrit 2.1.2.3. I'd appreciate any ideas on how to approach this.

-Nick

[Nicholas Mucci]

As an update to this, I've seen additional odd behavior from Gerrit
when a user cherry picks a change that is up for review in one
project, and tries to push it to a review in another project, much
like the earlier problems.

-Nick