Bug 1706834 - Document to let the admin know to check the cluster health while the upgrade playbook runs [upgrade playbook]
Summary: Document to let the admin know to check the cluster health while the upgrade ...
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 Async
Assignee: Anjana KD
QA Contact: Ashmitha Ambastha
URL:
Whiteboard:
Depends On:
Blocks: 1703695 1709460
TreeView+ depends on / blocked
 
Reported: 2019-05-06 11:30 UTC by Ashmitha Ambastha
Modified: 2019-11-25 06:35 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-25 06:35:50 UTC
Embargoed:


Attachments (Terms of Use)

Comment 9 Anjana KD 2019-11-11 13:21:05 UTC
Can this be added as a new Chapter in the Upgrade section?

Comment 10 Raghavendra Talur 2019-11-12 03:48:11 UTC
Yes, we should have a new chapter for "upgrade using the playbook".

There we should have the note which says it is in tech preview;
Then there will be a list of required and optional variables that need to be provided in the inventory.

Comment 12 Ashmitha Ambastha 2019-11-18 04:22:14 UTC
Hello, 

I see that this bug has been updated as a note in chapter 7: upgrading using the playbook. 
But, there are errors in the statement, which I think should be corrected.
@Anjana KD, please proofread before pushing changes and moving the bug to ON_QA. Moving this bug to FailedQA. Please reach out to me should you need any help. 

Please update this note: 

NOTE
While running the Openshift Container Storage upgrade playbook runs, the cluster admin needs to check the health of the cluster and all the pods and nodes in the cluster. The upgrade playbook does not fail or give a warning if app-pods running on the cluster fails or enters error state while the upgrade is in process. The cluster admin is to keep a check on the app-pods and the entire cluster health.

Comment 13 Anjana KD 2019-11-18 05:42:09 UTC
(In reply to Ashmitha Ambastha from comment #12)
> Hello, 
> 
> I see that this bug has been updated as a note in chapter 7: upgrading using
> the playbook. 
> But, there are errors in the statement, which I think should be corrected.
> @Anjana KD, please proofread before pushing changes and moving the bug to
> ON_QA. Moving this bug to FailedQA. Please reach out to me should you need
> any help. 
> 
> Please update this note: 
> 
> NOTE
> While running the Openshift Container Storage upgrade playbook runs, the
> cluster admin needs to check the health of the cluster and all the pods and
> nodes in the cluster. The upgrade playbook does not fail or give a warning
> if app-pods running on the cluster fails or enters error state while the
> upgrade is in process. The cluster admin is to keep a check on the app-pods
> and the entire cluster health.

Hello Ashmitha,

Based on our discussion in the office, I had added the above Note. Please let me know how could this be improved and could you provide more clarity. 
Just to be clear, I did proof-read the Note, still not sure what is wrong here.

Comment 14 Ashmitha Ambastha 2019-11-18 12:07:01 UTC
Hello Anjana, 

This is what is wrong,

NOTE
While running the Openshift Container Storage upgrade playbook runs*, the cluster-admin needs to check the health of the cluster and all the pods and nodes in the cluster. The upgrade playbook does not fail or give a warning if app-pods running on the cluster fails* or enters <into a> error state while the OCS* upgrade is in process. The cluster admin is to keep a check on the app-pods and the entire cluster* health.


I've marked the words that need change with an asterisk(*) and what I've added is within arrow brackets.
The note can be made shorter and more concise as well, but I leave it up to you to decide on that.

Comment 16 Ashmitha Ambastha 2019-11-22 03:26:12 UTC
LGTM, moving the bug to verified.


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