Snapshots left in undeletable state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Ollie Leahy | ||
Diablo |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If a volume is created using the euca api,
the snapshot cannot now be deleted. If the user tries
to delete the snapshot it ends up in the state 'error_deleting'
and remains in the system.
The following sequence of euca commands illustrates the problem
$ euca-create-volume -s 1 -z nova
VOLUME vol-0000007c 1 creating (bocktest, None, None, None) 2011-11-
# euca-create-
SNAPSHOT snap-00000018 vol-0000007c creating 2011-11-
# euca-delete-volume vol-0000007c# euca-delete-volume vol-0000007c
VOLUME vol-0000007c
# euca-delete-
SNAPSHOT snap-00000018
# euca-describe-
SNAPSHOT snap-00000018 vol-0000007c error_deleting 2011-11-
# euca-delete-
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
return_code = euca_conn.
File "/usr/lib/
return self.get_
File "/usr/lib/
raise self.ResponseEr
boto.exception.
<?xml version="1.0"?>
<Response>
Changed in nova: | |
milestone: | none → essex-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
assignee: | nobody → Ollie Leahy (oliver-leahy-l) |
Changed in nova: | |
milestone: | essex-2 → 2012.1 |
What volume driver do you use? Can you post nova-volume logs related to this bug?