Bug 1379063

Summary:	[Docs][HA] Instance HA removes the possibility use OSP-d for upgrades, documented procedure is needed
Product:	Red Hat OpenStack	Reporter:	Martin Schuppert <mschuppe>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED WONTFIX	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	7.0 (Kilo)	CC:	abeekhof, djuran, lbopf, mariel, michele, mschuppe, pablo.iranzo, royoung, rscarazz, srevivo, tvvcox
Target Milestone:	---	Keywords:	Documentation, Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-30 11:55:24 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:
Bug Depends On:	1484174, 1487994, 1488696, 1488697
Bug Blocks:

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