Unable to delete backups in error state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
stephen mulcahy |
Bug Description
Attempts to perform "cinder backup-delete" on a backup in error state causes the status to be changed to "available" and subsequent delete call results in a trace.
To reproduce:
shutdown the cinder-backup service
attempt to create a backup of a volume and watch it time out appropriately waiting for the service to respond
Then, start the service
Attempt to delete the backup that is now listed in error state
Traceback (most recent call last):
File "/opt/stack/
rval = self.proxy.
File "/opt/stack/
return getattr(proxyobj, method)(ctxt, **kwargs)
File "/opt/stack/
raise exception.
InvalidBackup: Invalid backup: delete_backup aborted, the backup service currently configured [cinder.
This is a good check to have, but we need some method of deleting failed backups regardless of the service that created them, at least in the case of failed backups.
Changed in cinder: | |
assignee: | nobody → stephen mulcahy (stephen-mulcahy) |
Changed in cinder: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-1 → 2013.2 |
Fix proposed to branch: master /review. openstack. org/26103
Review: https:/