Bug 1576161

Summary:	output / reason of compare-bug-and-report should be added along with 'FAILURE'
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, gluster-infra, nigelb, srangana
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Process-Automation
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-03 10:08:40 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 Amar Tumballi 2018-05-09 03:05:42 UTC

# Description of problem:

There are 4 major reason for failure of Bugzilla check in smoke.

1. No Reference (BUG/Issue) ID
2. Product is not GlusterFS
3. Posted Bug Status is not valid
4. Posted Bug is not marked for relevant release version. (like a bug of 4.0 version is posted for release-4.1 branch).

Would be great to see the reason coming out to gerrit itself, saves time to go to job output.

# Additional info:

We have something like this in 'comment-on-issues' where if the DocApproved and SpecApproved is missing, we get a notice in smoke itself.

Comment 1 Nigel Babu 2018-08-03 10:08:40 UTC

This is now fixed.