yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #09394
[Bug 1277339] [NEW] snapshot-failed-when-dependent-volume-exist
Public bug reported:
When we use 'HpSanISCSIDriver ', there is some issues.
1. Create volume
2. Create snapshot from volume
3. Create new volume from snapshot
4. Try to delete snapshot.
In this work flow, the status of snapshot should be 'error_deleting'.
The error message says like this.
<gauche version="1.0">\n\n <response description="Volume delete
operation failed: \'\'The snapshot \'snapshot-d357590a-47f7-4785-bd6b-
debce5bd9a2a\' cannot be deleted because it is a clone point. When
multiple volumes depend on a snapshot, that snapshot is a clone point.
To delete the clone point, you must first delete all but one of the
volumes that depend on it.\'\'" name="CliqOperationFailed"
processingTime="330" result="80001010"/>\n\n</gauche>
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1277339
Title:
snapshot-failed-when-dependent-volume-exist
Status in OpenStack Compute (Nova):
New
Bug description:
When we use 'HpSanISCSIDriver ', there is some issues.
1. Create volume
2. Create snapshot from volume
3. Create new volume from snapshot
4. Try to delete snapshot.
In this work flow, the status of snapshot should be 'error_deleting'.
The error message says like this.
<gauche version="1.0">\n\n <response description="Volume delete
operation failed: \'\'The snapshot \'snapshot-d357590a-47f7-4785-bd6b-
debce5bd9a2a\' cannot be deleted because it is a clone point. When
multiple volumes depend on a snapshot, that snapshot is a clone point.
To delete the clone point, you must first delete all but one of the
volumes that depend on it.\'\'" name="CliqOperationFailed"
processingTime="330" result="80001010"/>\n\n</gauche>
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1277339/+subscriptions
Follow ups
References