Bug 1633487

Summary:	smoke failure during backport
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, nigelb
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:	2018-10-03 04:26:26 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 Sanju 2018-09-27 06:55:55 UTC

Description of problem:
When we backport a change from master to any other  release branch, commit message of the change in master has "fixes : bz#n" and we also add another "fixes: bz#n" for referring to the BZ raised against that specific version. Smoke test is taking the first "fixes: bz#n" and checking whether the BZ is raised for the correct version and product. As the version is different and it finds another field "fixes: bz#n", the smoke is failing.

Version-Release number of selected component (if applicable):


How reproducible:
always during  backport.

Comment 1 Nigel Babu 2018-09-27 07:11:57 UTC

I've added a tweak to the python scripts to handle this: https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/168

Comment 2 Nigel Babu 2018-09-27 11:27:25 UTC

Great, so it appears all our scripts actually break around this - SO when you do backports, things will break. People work around it by changing Fixes/Updates -> Bug for the old bug.

Comment 3 Nigel Babu 2018-10-03 04:26:26 UTC


*** This bug has been marked as a duplicate of bug 1618407 ***