Bug 1645776

Summary:	Consider gd2-smoke as part of main vote
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	project-infrastructure	Assignee:	bugs <bugs>
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-09 05:45:48 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 Atin Mukherjee 2018-11-03 15:23:29 UTC

Description of problem:

As of now the vote for the job gd2-smoke was considered as optional. With GD2 getting more stable and the smoke of GD2 being green for more than multiple weeks, this is a proposal to consider the voting of gd2-smoke to be strict on glusterfs so that changes to any of the repos in GD2 & glusterfs do not break each other going forward.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Atin Mukherjee 2018-11-08 06:29:14 UTC

Nigel - seems like even though the change is now in, we're having some spurious issues on GD2 tests and some of the smokes are failing. Can we please revert this change till we address this issue, keep the smoke results monitored for two more weeks and then re-enable it?

Comment 2 Nigel Babu 2018-11-09 05:45:48 UTC

This has been reverted. Please open a new bug to request re-enabling the voting.