Add the ability to create a Cinder volume with a predefine UUID
Bug #1705891 reported by
Maor Lipchuk
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
If we consider an admin of a management platform which integrates with Cinder, one would like to have the ability to remove any redundant Cinder volumes which were created as part of any failing transactions in the management platform.
The admin could encounter a scenario where one created a volume using the Cinder API and then the management platform crashes without being aware whether of the volume status.
It could be a very convenient feature if the admin could pass the UUID which the volume should be created with and by that can verify, very easily, in case of a crash, whether this volume was created or not and remove it if necessary.
Revision history for this message
| Gorka Eguileor (gorka) wrote | #1 |
| Changed in cinder: | |
| status: | New → Invalid |
To post a comment you must log in.
Cinder community has discussed this before and it was agreed that we won't allow reusing UUIDs, so in your scenario providing the UUID would not be allowed, since that UUID already existed.
Also, even if the backend failed during the operation the driver should be smart enough to check if it exists when a delete request is received on Cinder. If it's not doing that then a bug could be opened for that driver to fix that situation.