Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691773 - OCS 3.11 Operations Guide: Describe steps how to do maintenance on OCS nodes [NEEDINFO]
Summary: OCS 3.11 Operations Guide: Describe steps how to do maintenance on OCS nodes
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: Unspecified
OS: Linux
Target Milestone: ---
: ---
Assignee: Chandrakanth Pai
QA Contact:
Depends On:
Blocks: 1694089
TreeView+ depends on / blocked
Reported: 2019-03-22 13:48 UTC by Patric Uebele
Modified: 2019-04-11 07:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
chpai: needinfo? (madam)

Attachments (Terms of Use)

Description Patric Uebele 2019-03-22 13:48:57 UTC
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36
Build Identifier: 

Please add a section to the OCS Operations Guide that describes the necessary steps that need to be taken before and after doing maintenance (e.g. installation of OS patches) of OCS nodes in a cluster. Especially waiting for gluster heals to finish.

Reproducible: Always

Comment 2 RamaKasturi 2019-04-05 13:01:23 UTC
Hello Anjana,

   Do we have a draft steps available for this as i see that it needs some testing to be done.


Comment 3 Chandrakanth Pai 2019-04-08 05:27:16 UTC
Hi Patric,

Could you please provide the required steps so that I can come up with a draft before QE tests it?


Comment 4 Chandrakanth Pai 2019-04-08 06:16:12 UTC
@Michael, could you please help in providing the required steps?


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