Bug 1683696 - 6.1.3. Upgrading the Red Hat Gluster Storage Pods section needs an update
Summary: 6.1.3. Upgrading the Red Hat Gluster Storage Pods section needs an update
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
high
Target Milestone: ---
: OCS 3.11.z Batch Update 2
Assignee: Bhavana
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: 1672844
TreeView+ depends on / blocked
 
Reported: 2019-02-27 15:12 UTC by Anjana Suparna Sriram
Modified: 2019-04-01 06:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-01 06:08:08 UTC
Embargoed:


Attachments (Terms of Use)

Description Anjana Suparna Sriram 2019-02-27 15:12:44 UTC
https://access.qa.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Upgrade-Gluster_pods

Raising this bug to remove the step to restart the gluster pods for the 2nd time as part of the upgrade process. OCS 3.11.2 consumes RHGS 3.4 BU3 which has the fix of BZ 1651460, we need to take out this step.

Comment 5 RamaKasturi 2019-03-18 05:51:02 UTC
Moving the bug to assigned state as i still see that the second pod restart is present where as this should be removed as per the description of the bug.

Comment 10 RamaKasturi 2019-03-20 12:08:22 UTC
Verified in the pdf attached at comment 8 for 3.11 docs and i see that step 16 in 6.1.3 section is removed where gluster pod reboot is done after setting the op-version.

Verified in the pdf attached at comment 8 for 3.11 docs and i see that step to reboot gluster pods is removed after setting up the op-version. 

Moving the bug to verified as the changes looks good to me.


Note You need to log in before you can comment on or make changes to this bug.