Bug 1382170

Summary: Documentation: We need to add a note upgrade guide to check the pcs cluster state before each step of overcloud upgrade.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: dmacpher, mburns, sasha, srevivo, tvignaud
Target Milestone: asyncKeywords: Documentation
Target Release: 9.0 (Mitaka)   
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: 2016-12-01 04:52:18 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:

Description Alexander Chuzhoy 2016-10-05 23:30:45 UTC 
Documentation: We need to add a note upgrade guide to check the pcs cluster state before each step of overcloud upgrade.

I didn't find such a note here:
https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/upgrading-red-hat-openstack-platform/chapter-3-director-based-environments-performing-upgrades-to-major-versions

The pcs cluster should have no stopped resources before proceeding to the next step.
Comment 2 Dan Macpherson 2016-10-19 03:44:07 UTC 
Hi Sasha,

I've added the following note to each step:

===
Note

Login to a Controller node and run the pcs status command to check if all resources are active in the Controller cluster. 
===

This should be live on the portal now.

Was there anything further required for this BZ?
Comment 3 Dan Macpherson 2016-12-01 04:52:18 UTC 
No response in over a month. Closing this BZ but feel free to reopen if further changes are required.