Red Hat Bugzilla – Bug 1477390
Inconsistency between contents
Last modified: 2018-01-07 05:32:15 EST
Description of problem:
In upgrade guide for Red Hat OpenStack Platform 8, Compute nodes , 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 , there is a sentence added 4 months ago,
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 .
"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 >.
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.
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.
No prob. Thanks for reporting this issue!