Bug 1683726

Summary:	[Doc] Reverse upgrade steps so that Heketi pod start up is before updating client rpms on all OCP nodes
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	khartsoe <khartsoe>
Component:	doc-Container_Native_Storage_with_OpenShift	Assignee:	Chandrakanth Pai <chpai>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RamaKasturi <knarra>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	amukherj, asriram, chpai, knarra, rhs-bugs, rtalur, sankarshan, storage-doc
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 3
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-07-22 13:29:33 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:
Bug Depends On:
Bug Blocks:	1694089

Comment 2 RamaKasturi 2019-04-05 12:33:46 UTC

Hello Anjana / Talur,

   If i remember right, we made the change of bringing down heketi and bringing it back once all the clients are updated during experian Testing. Now the bug says we will have to move bringing back heketi up before updating the client rpms ? Are we okay to do this ? Can you confirm ?  If yes, i would like to understand why we did this during experian. just want to be sure before i ack .

@Anjana, we would need to do this change at both the docs 3.10 & 3.11, just FYI.

Thanks
kasturi

Comment 8 RamaKasturi 2019-04-15 12:04:00 UTC

Acking this bug for 3.11.3