upgrade levels

Bug #1942847 reported by Rafal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Operators
New
Undecided
Unassigned

Bug Description

Documentation regarding upgrade_levels in operations guide may be misleading.

https://docs.openstack.org/operations-guide/ops-upgrades.html

It suggests that upgrade level should be locked to version X+1 (new one?) where in fact it should be locked to current (old) one.

It is:

[upgrade_levels]
compute=X+1
conductor=X+1
scheduler=X+1

It should be:

[upgrade_levels]
compute=X
conductor=X
scheduler=X

This is also correctly described in nova's documentation of this configuration option:

https://github.com/openstack/nova/blob/master/nova/conf/upgrade_levels.py#L35

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.