Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1490775

Summary:	[3.12] does not have the permission for tagging
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, nigelb, srangana
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-12 08:53:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiffin 2017-09-12 08:31:34 UTC

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    
To ssh://thotz.org/glusterfs
 ! [remote rejected] v3.12.1a -> v3.12.1a (prohibited by Gerrit)
error: failed to push some refs to 'ssh://thotz.org/glusterfs'
Version-Release number of selected component (if applicable):
release 3.12

How reproducible:
always


Additional info:
Only permission for tagging is not available, but I can run submit patches, run release job etc.

Comment 1 Jiffin 2017-09-12 08:53:27 UTC

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

Comment 2 Nigel Babu 2017-09-12 11:37:00 UTC

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.

Comment 3 Niels de Vos 2017-09-12 12:04:24 UTC

It is recommended to sign a tag with a gpg key. In that case, "git tag -s ..." will show the usual editor.

Comment 4 Shyamsundar 2017-09-12 12:10:40 UTC

@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.