Bug 1663089

Summary:	Make GD2 container nightly and push it docker hub
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:	2019-01-03 10:07:56 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 2019-01-03 06:12:45 UTC

Description of problem:

During GCS scale testing effort, we identified couple of major issues in GD2 for which the PRs were posted and merged yesterday night, but apparently they missed the window of yesterday's nightly build and hence we're sort of blocked till today evening for picking up the GD2 container image.

If we can build the container from the latest GD2 head and push it to docker hub right away, it'd be great and we should get unblocked.

Comment 1 Nigel Babu 2019-01-03 06:15:05 UTC

Did it make it to the GD2 nightly RPM build?

Comment 2 Atin Mukherjee 2019-01-03 07:00:46 UTC

As per https://ci.centos.org/view/Gluster/job/gluster_gd2-nightly-rpms/ , it seems like the last build was 6 hours 49 minutes ago which means the required PRs should be in as part of the rpms.

Comment 3 Nigel Babu 2019-01-03 10:07:56 UTC

ALright, Deepshika retriggerd the Jenkins job and we're good now.