Bug 1683726 - [Doc] Reverse upgrade steps so that Heketi pod start up is before updating client rpms on all OCP nodes
Summary: [Doc] Reverse upgrade steps so that Heketi pod start up is before updating cl...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: OCS 3.11.z Batch Update 3
Assignee: Chandrakanth Pai
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: 1694089
TreeView+ depends on / blocked
 
Reported: 2019-02-27 16:23 UTC by khartsoe@redhat.com
Modified: 2019-07-22 13:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-22 13:29:33 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.