volume is not available when create backups from snapshots
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
wangxiyuan |
Bug Description
Now when users try to create a backup from a snapshot, the volume related to the snapshot is set to backing-up during the action and can't be used for other actions. It's strange that the volume is not available though the backup create action is not related to it.
When create a backup from a large snapshot, such as larger than 1 TB, It will costs few hours generally. It's really a problem that the volume is not available for such a long time.
We need to set the right resource's status to "backing-up" when create backups from resources. We could do a check in the backup API to see whether snapshot_id is provided or not. If provided, we change the status of the snapshot; otherwise, we change the status of the volume as usual.
Changed in cinder: | |
assignee: | nobody → wangxiyuan (wangxiyuan) |
Changed in cinder: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. openstack. org/442241
Review: https:/