fc51678298
After live migrating a volume into the 3PAR driver the volume would be unusable. And we would no longer be able to do any operation with it. Migrated in-use volumes cannot be renamed when migrated and therefore need to use the "_name_id" field of the Volume object (volumes table in the DB) to store the original volume's ID so the driver can locate the volume. The problem is that, even though the 3PAR driver sets the "_name_id" field, it doesn't use it for any operation, so once the volume has been migrated and the ID of the volume no longer matches the one that was used to create the volume (value now in "_name_id") it will no longer be able to locate the volume. This patch adds the logic necessary to locate volumes using the "_name_id" field. Closes-Bug: #1697422 Change-Id: I27b9d4be419e1b52db02d4525b292ceeb5d5f867
8 lines
262 B
YAML
8 lines
262 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fix HPE 3PAR driver issue where volumes that were live migrated to it would
|
|
end up being inaccessible. We would no longer be able to use the volume
|
|
for any operation, such as attach, detach, delete, snapshot, etc.
|
|
(bug 1697422)
|