Bug 1718982

Summary:	Heketi spec contains old reference to image tag
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	John Mulligan <jmulligan>
Component:	heketi	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED ERRATA	QA Contact:	Aditya Ramteke <aramteke>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aramteke, hchiramm, kramdoss, madam, puebele, rhs-bugs, rtalur, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhgs-volmanager-container-3.11.5-1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-26 20:05:00 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 John Mulligan 2019-06-10 16:52:30 UTC

The Heketi spec file changes the built-in value of the container image, but the value it sets refers to a rather old tag of the volmanager image.

We should a) investigate if this is still needed and b) if so, update the tag to something more appropriate.

Comment 10 Raghavendra Talur 2020-01-22 15:54:58 UTC

Summary:
In OCS installation process, first we deploy deploy-heketi and gluster pods. We load the json into deploy-heketi, create the cluster based on json. Then run the setup-openshift-heketi-storage job which creates a job specification for the migration of the db. Then once the migration is complete, we deploy heketi. When heketi is ready, deploy-heketi is destroyed. 

The code change made for this bug is to change the image that is used for the migration of the db. There is no other way to test for this except interrupting the installation as mentioned in the previous comment and then manually observing the copy job specification.

Regression testing is simpler: If the installation succeeds then it means the change in the image name hasn't impacted us in any way.

Comment 13 errata-xmlrpc 2020-02-26 20:05:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0621