530376bc5d
In some deployments, after an upgrade, we remove the old service
records and create new ones. This leaves the volumes with the
service_uuid pointing to the old (deleted) service and causes an
issue while purging out the deleted service records.
This patch adds a cinder-manage command to update the
service_uuid field of volumes with the following command:
``cinder-manage volume update_service``
The service_uuid of volumes associated with old service_uuid
also gets updated when cinder creates a new service.
Change-Id: I0b13c6351733b8163bcf6e73c939c375493dcba5
(cherry picked from commit edeac132a1)
16 lines
693 B
YAML
16 lines
693 B
YAML
---
|
|
features:
|
|
- |
|
|
Added a new cinder-manage command to handle the situation where database
|
|
purges would not complete due to the volumes table holding references to
|
|
deleted services. The new command makes sure that all volumes have a
|
|
reference only to the correct service_uuid, which will allow old service
|
|
records to be purged from the database.
|
|
|
|
Command: ``cinder-manage volume update_service``
|
|
- |
|
|
When Cinder creates a new cinder-volume service, it now also immediately
|
|
updates the service_uuid for all volumes associated with that
|
|
cinder-volume host. In some cases, this was preventing the database purge
|
|
operation from completing successfully.
|