Description of problem:
Not able to push tag created into release branch 3.12
# git tag v3.12.1a release-3.12
# git push --tags origin release-3.12
Total 0 (delta 0), reused 0 (delta 0)
remote: Processing changes: refs: 1, done
! [remote rejected] v3.12.1a -> v3.12.1a (prohibited by Gerrit)
error: failed to push some refs to 'ssh://email@example.com/glusterfs'
Version-Release number of selected component (if applicable):
Only permission for tagging is not available, but I can run submit patches, run release job etc.
After discussing issue with talur, he have mentioned we need to provide message for tagging otherwise gerrit will reject.
"git tag -m "3.10.2 GA" v3.10.2"
Hence for the time being closing this bug, will reopen the bug if issues again hit
Both Jiffin and I expected an editor to pop up when you do the git-tag command without a message. That didn't happen and lead to the issue.
It is recommended to sign a tag with a gpg key. In that case, "git tag -s ..." will show the usual editor.
@jiffin, @talur, we have: https://hackmd.io/JwQwZgphBMCsAsBaAzAYxMR8wEYAciwA7MhIgEbnwAm1ycss0EQA# from Kaushal which we follow religiously to tag and create release branches.
This is cross referenced here: https://hackmd.io/IwEwnArApmYIYFoDGAjEUEBYSYgucAZosMAAwhnBRkBMUuQA#
It would be nice if we used these instructions, and improved on them.