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

Bug 1636455

Summary:	gluster bot is not changing the status of bug
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED CURRENTRELEASE	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-11-12 09:20:41 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-10-05 12:51:56 UTC

Description of problem:
When we post a patch for review in gerrit, gluster bot will update the associate BZ with the details patch. But gluster bot is not changing the status of the bug.
Even though the patch is posted, the bug is in assigned state only.

After merging patch also, gluster bot is updating the BZ with a comment saying "this commit has merged", but status is not changed to Modified.

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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
status of bug is never changed

Expected results:
Bug status should be changed accordingly.

Additional info:

Comment 1 Nigel Babu 2018-10-05 12:55:44 UTC

Huh, I seemed to have missed this completely in the python script. I've reverted back to the old bash script. I'm going to add this and the external bug tracker review in one go. Tracking for sprint 5.

Comment 2 Nigel Babu 2018-11-12 09:20:41 UTC

Fixed in https://github.com/gluster/glusterfs-patch-acceptance-tests/commit/cf632e8329a36337c0bb3f9fd52ec3fb67fb1b07