Should check cinder-backup service before changing to "backing-up"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Ken'ichi Ohmichi |
Bug Description
If cinder-backup service is not enabled, "cinder backup-create" command fails
like the following. As the result, the volume status has been changed to
"backing-up" in spite of not backing-up.
$ cinder backup-create vol-test
ERROR: Service cinder-backup could not be found.
$ cinder list
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| f48aa6ae-
+------
$
On default policy, a volume status can be changed by admin only.
So it is better to check the cinder-backup existence before changing a volume status.
Changed in cinder: | |
status: | In Progress → Triaged |
importance: | Undecided → Medium |
milestone: | none → havana-rc1 |
Changed in cinder: | |
status: | Triaged → In Progress |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-rc1 → 2013.2 |
Fix proposed to branch: master /review. openstack. org/45169
Review: https:/