Comment 0 for bug 1813138
Revision history for this message
| Silvan Kaiser (2-silvan) wrote incorrect volume provider_location after snapshot deletion with attached volume in remotefs driver | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
tl;dnr:
The _snapshot_exists method should return false if all snapshots have been deleted, even if the last snapshot was deleted via the Nova API.
Detailed:
Using the RemoteFSSnapDri
1) Create a volume and attach it to a VM
2) Create a snapshot file for this volume
3) Delete the snapshot file
4) Compare the volumes provider_location attribute to the path stored in the volumes .info file, they differ (which they should not).
The reason for this is that when deleting the last snapshot of a volume via Nova API the resulting file is not the original volume file but the file created during snapshotting, as Nova uses a pull operation (see [2]). This behaviour differs from the deletion of a snapshot of a detached volume [3], where the volumes file name stays the original file name.
This issue arises when the _snapshot_exists method [4] compares the active image path to the volumes path (which is based on the volume.
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] https:/