upgrades: purge old compute service entries
Add pre-upgrade step to discover and purge and old compute service entries; in later openstack releases, the DB model will throw exceptions for service entries with versions less than the minimum requirement, causing API requests to error post upgrade. Change-Id: Id739f0f23aaadf08dff216bb9f17552deee1b0a4 Closes-Bug: 1809260
This commit is contained in:
parent
ba63ff107e
commit
5b82aa4814
|
@ -123,6 +123,25 @@ archive of nova data run the nova-cloud-controller action:
|
|||
This action may need to be run multiple times until the action output reports
|
||||
'Nothing was archived'
|
||||
|
||||
2.4 Purge old compute service entries
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Old service entries for compute services on units which are no longer part of
|
||||
the model should be purged before upgrade.
|
||||
|
||||
Any old service entries will show as 'down' and on machines no longer in the
|
||||
model when looking at the current list of compute services:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
openstack compute service list
|
||||
|
||||
Services can be removed using the 'compute service delete' command:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
openstack compute service delete <ID of service>
|
||||
|
||||
|
||||
3. Upgrade Order
|
||||
----------------
|
||||
|
|
Loading…
Reference in New Issue