volume stays in an indefinite "backing-up" state when no cinder-backup is running
Bug #1200040 reported by
Steve Baker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Xiaoxi Chen |
Bug Description
Creating a backup when cinder-backup is not running results in the following:
- the volume going into state "backing-up"
- the backup going into state "creating"
This state continues indefinitely, even when no backup is actually occurring.
It would be better if this failed immediately with a backup unavailable error.
Changed in cinder: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in cinder: | |
assignee: | nobody → xiaoxi_chen (xiaoxi-chen) |
Changed in cinder: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Furthermore if you start cinder-backup all started backups will be set to 'error'.
See backup/manager.py:
115 # TODO(smulcahy) implement full resume of backup and restore backup_ get_all_ by_host( ctxt, self.host) _('Resetting backup %s to error ' backup_ update( ctxt, backup['id'], {'status': 'error',
116 # operations on restart (rather than simply resetting)
117 backups = self.db.
118 for backup in backups:
119 if backup['status'] == 'creating':
120 LOG.info(
121 '(was creating)') % backup['id'])
122 err = 'incomplete backup reset on manager restart'
123 self.db.
124 'fail_reason': err})