Bug 1379063 - [Docs][HA] Instance HA removes the possibility use OSP-d for upgrades, documented procedure is needed
Summary: [Docs][HA] Instance HA removes the possibility use OSP-d for upgrades, docume...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1484174 1487994 1488696 1488697
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-24 14:11 UTC by Martin Schuppert
Modified: 2021-08-30 12:09 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-30 11:55:24 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2661641 0 None None None 2016-09-27 11:33:43 UTC

Description Martin Schuppert 2016-09-24 14:11:10 UTC 
Description of problem:
A lot of customers have already enabled or test instance HA. 

As listed in [1]:
* No overcloud stack updates will be run following the configuration of instance HA. 

A documented procedure is needed for customers enabled instance HA to temporary disable it and enable it afterwards. This is critical since customers probably do NOT check this requirement before performing the upgrade.

This is needed for starting for OSP7 where we introduced instance HA.

[1] https://access.redhat.com/documentation/en/red-hat-openstack-platform/version-8/high-availability-for-compute-instances/

Version-Release number of selected component (if applicable):
OSP7,OSP8,OSP9

How reproducible:
install OSP7, enable instance HA, perform upgrade to OSP8 using Director.
Comment 10 Andrew Beekhof 2018-08-30 11:55:24 UTC 
Closing.
- It does not appear that this is affecting customers
- There are notes in other areas (ie. the 6->8 FFU upgrade)
- There is a knowledge base article that covers the issue
- Realistically there is unlikely to be doc capacity to address this
Note You need to log in before you can comment on or make changes to this bug.