Bug 1477390

Summary: Inconsistency between contents
Product: Red Hat OpenStack Reporter: Shinobu KINJO <skinjo>
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: augol, dmacpher, jfrancoa, mandreou, mburns, skinjo, srevivo
Target Milestone: ---Keywords: Triaged
Target Release: ---   
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: 2017-08-04 03:44:39 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:
Embargoed:

Description Shinobu KINJO 2017-08-02 00:25:02 UTC
Description of problem:
-----------------------
In upgrade guide for Red Hat OpenStack Platform 8, Compute nodes [1], we explicitly describe < ensure zero downtime > in section 3.4.5:

******
3.4.5. Upgrading Compute Nodes

We perform the following task on each node individually to ensure zero downtime. Select a Compute node to upgrade. 

Migrate its workload. See "Migrating VMs from an Overcloud Compute Node" in the Red Hat OpenStack Platform Director Installation and Usage Guide. 
*****

In the same guide in different page [2], there is a sentence added 4 months ago, 

******
Warning
Before performing an upgrade to the latest major version, ensure the undercloud and overcloud are updated to the latest minor versions. This includes both OpenStack Platform services and the base operating system. For the process on performing a minor version update, see "Updating the Environment" in the Red Hat OpenStack Platform 7 Director Installation and Usage guide. Performing a major version upgrade without first performing a minor version update can cause failures in the upgrade process. 
******

There is a description as below in that sentence, this is linked to different content [3].

"Updating the Environment"

In that contents, there is a sentence as below. Here we explicitly describe < If required, perform a reboot manually after the update command completes >.

******
Important
The update process does not reboot any nodes in the Overcloud automatically. If required, perform a reboot manually after the update command completes. 
******

We are saying that ** zero downtime is doable **. But we are also saying that ** perform a reboot after the update command complete **.

Those kind of ambiguous description could make the customers confused, especially the customers who do want to avoid any downtime.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/html/upgrading_red_hat_openstack_platform/chap-upgrading_the_environment#sect-Major-Upgrading_the_Overcloud-Compute

[2] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/html/upgrading_red_hat_openstack_platform/chap-upgrading_the_environment

[3] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/director_installation_and_usage/sect-updating_the_overcloud#sect-Updating_the_Overcloud_Packages

Comment 6 Jose Luis Franco 2017-08-03 08:46:27 UTC
Hi Dan,

It was discussed during yesterday's DFG scrum that this bug had been assigned to DFG Upgrades, so I offered myself to take care of it. But I see you have it already narrowed down.
If there is anything I can help with, just let me know.

Jose

Comment 10 Dan Macpherson 2017-08-04 03:44:39 UTC
No prob. Thanks for reporting this issue!