Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1515334 - [RFE] Undercloud on N+3 needs to be compatible with an overcloud in N
Summary: [RFE] Undercloud on N+3 needs to be compatible with an overcloud in N
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-20 15:31 UTC by Yolanda Robla
Modified: 2019-04-15 05:51 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Yolanda Robla 2017-11-20 15:31:14 UTC
Description of problem:

In the scope of fast forward upgrades, one of the steps is upgrading the undercloud to N+3, while the overcloud remains on N.

This needs to be done in a maintenance window, while the overcloud upgrade doesn't come until the next maintenance window. These maintenance windows have a max of 4 hours, and we need to be able to perform full steps that can be isolated on that time, including the time for backup, testing and restore
The system needs to be on an usable state after each of the maintenance window steps. But we hit a problem on undercloud upgrade.

When we upgrade undercloud to n+3 the overcloud is still on 10. This means the overcloud is still up, but we are not able to control the status via undercloud. Things like removing a node, or creating a new one, are failing because there is no API compatibility between N and N+3.

For fast forward upgrade process to be successful on a production environment, we need to have compatibility between N and N+3 in terms of undercloud/overcloud.

Right now when having undercloud on pike and overcloud on newton, it failed because a disruptive change on os-hypervisors API, but i guess more failures will happen. There is a need to test the undercloud on N+3 behaviour properly with an N overcloud.

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