Bug 1689380

Summary:	heketi registry pods needs to be brought up once they are brought down for glusterfs upgrade.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	doc-Container_Native_Storage_with_OpenShift	Assignee:	storage-doc
Status:	CLOSED CURRENTRELEASE	QA Contact:	RamaKasturi <knarra>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	asriram, pasik, rhs-bugs, 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:30:03 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

Description RamaKasturi 2019-03-15 18:42:47 UTC

Description of problem: As of now in the docs i do not see a step to bring up heketi registry pods once they are down for glusterfs upgrade. We need to make sure that we add a note for the same.

Doc URL : https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/

SectionName & Number : Needs to be added both in independent and converged mode sections.

Suggestions for Improvement : Add a note asking the customer/user to bring back heketi registry pod which was brought down during glusterfs upgrade.

Additional Info : Refer updating client on RedHat Openshift container platform nodes section for more info on how to bring back heketi pod.

Comment 2 RamaKasturi 2019-04-05 12:55:04 UTC

Acking the bug for 3.11.3

Comment 5 RamaKasturi 2019-04-26 13:40:39 UTC

Hello Bhavana,

   When we deploy OCP + OCS with both app & infra storge present, user needs to upgrade heketi & glusterfs pods in both the namespaces and scale them down in both namespaces. Hence having it in 6.2.3 may not be sufficient due to the fact that we do not have any note either in 6.2.3 or in the registry section asking customer to bring back their heketi registry pod. A note in one of the section would do it .

Thanks
kasturi