Cinder migration may leave stale volumes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
High
|
Alon Marx |
Bug Description
When performing cinder migration, if the storage connectivity from the cinder node to the storage fails, the volume will not be found as expected.
In that case, looks like cinder attempts a rollback by trying to delete the volume it created for the migration at the destination.
*The issue*
the rollback action does not perform a 'detach' prior to 'delete volume'.
In case of some storage vendors, volume delete will fail because the volume is still attached to the host (at the storage array side).
This leaves stale volumes on the storage arrays at the destination.
*Solution*
Perform 'detach' before attempting to 'delete' the volume
*Log from the migration is attached*
migration starts at the beginning of the log
source vol: f3316fc0-
dest host to migrate to: nova3.ps.
Alon, can you please take a look at this. Appears that it was seen on XIV doing migration.
Thanks!