Bug 1474690 - [Doc] Suggestion for improving upgrade doc OSP11
[Doc] Suggestion for improving upgrade doc OSP11
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation (Show other bugs)
11.0 (Ocata)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: RHOS Documentation Team
RHOS Documentation Team
Depends On:
  Show dependency treegraph
Reported: 2017-07-25 03:25 EDT by Chaitanya
Modified: 2017-07-25 20:27 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-25 20:27:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chaitanya 2017-07-25 03:25:53 EDT
Description of problem:
Under the section 3.4.1- Upgrading the Director 4th point, we have an 'Important' section which states that the default provisioning / control plane has changed from to https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/upgrading_red_hat_openstack_platform/#sect-Major-Updating_Director_Packages

It states to check certain parameters in undercloud.conf file like local_ip, network_gateway etc. and in the end its asks the users to make sure that the undercloud.conf file is proper before running the undercloud upgrade.

This section is confusing and it does not clearly mention what needs to be done if default provisioning plane is configured: Do we have to change it to in the undercloud.conf file and run the upgrade / keep the undercloud.conf file as it is.

The solution to this is known when we go through the install-undercloud.log file     for OSP10 which states the following:

The old default CIDR of is deprecated due to it being an
unroutable address range under RFC 5737.  This default will change in the
Ocata release of OpenStack, so you should stop using the default CIDR and set
a valid, routable CIDR instead.

Note that if you have already deployed an overcloud with the
CIDR, it will not be possible to change it without re-deploying.  If the
overcloud cannot be re-deployed, you must explicitly set the network values
in undercloud.conf to ensure continued use of the CIDR during
future upgrades.

Solution: Explicitly set the network values in undercloud.conf to ensure continued use of the CIDR during future upgrades.

I think it would be great if we can include some of this text to the undercloud upgrade documentation to avoid confusion. 

Version-Release number of selected component (if applicable):
Comment 1 Dan Macpherson 2017-07-25 09:23:28 EDT
Hi Chaitanya,

I've revised the text in the section your specified:

"The default Provisioning/Control Plane network has changed from to If you used default network values in your previous undercloud.conf file, your Provisioning/Control Plane network is set to This means you need to set certain parameters in your undercloud.conf file to continue using the network. These parameters are:

etc, etc, etc"


How does that read now? Does it clarify what the user needs to do?
Comment 2 Chaitanya 2017-07-25 09:40:18 EDT
Hi Dan,

  Thanks for the revision.

Can you include the following text in the end(or something like):

you must explicitly set the network values in undercloud.conf to ensure continued use of the CIDR during future upgrades.

That would be more clear to understand.
Comment 4 Chaitanya 2017-07-25 11:24:08 EDT
Hi Dan,

 That looks perfect now.

Comment 5 Dan Macpherson 2017-07-25 20:27:09 EDT
No prob. Thanks for highlighting this.

Note You need to log in before you can comment on or make changes to this bug.