Bug 1381355 - upgrade docs for non-director should mention starting the database before running openstack-db commands
Summary: upgrade docs for non-director should mention starting the database before run...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 19:43 UTC by Jeremy
Modified: 2019-12-16 06:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-01 04:51:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jeremy 2016-10-03 19:43:36 UTC 
Description of problem:
Non-director upgrade doc says use openstack-db to upgrade database schema but the database will be down since the previous step says do pcs property set stop-all-resources=true to stop all resources including the Database.

Version-Release number of selected component (if applicable):
https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/upgrading-red-hat-openstack-platform/chapter-4-non-director-environments-upgrading-openstack-services-simultaneously
Comment 1 Jeremy 2016-10-03 19:46:05 UTC 
Also: 
Under the section : 4.4. ENABLING ALL OPENSTACK SERVICES
IT says restart services using # pcs property set stop-all-resources=false
, then it says Wait until all resources have stopped.  Looks like a copy paste error from the previous section 4.1 that tells you to stop services with  pcs property set stop-all-resources=true..
Comment 3 Dan Macpherson 2016-10-25 06:30:17 UTC 
Hi Jeremy,

I've added instructions to set the load balancing and database services to unmanaged before you use the stop-all-resources flag. This should ensure the unmanaged services stay up and provide an active db communication:

Here's an example:

https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/upgrading-red-hat-openstack-platform/#disabling_all_openstack_services

I also fixed the item in comment #1

How does it look to you? Is there anything else I might need to include for this section?
Comment 4 Dan Macpherson 2016-12-01 04:51:23 UTC 
No response in over a month. Closing this BZ, but feel free to reopen if further changes are required.
Note You need to log in before you can comment on or make changes to this bug.