volume is not available when create backups from snapshots

Bug #1670541 reported by wangxiyuan
6
This bug affects 1 person
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.

wangxiyuan (wangxiyuan)
Changed in cinder:
assignee: nobody → wangxiyuan (wangxiyuan)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/442241

Changed in cinder:
status: New → In Progress
Xing Yang (xing-yang)
Changed in cinder:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/442241
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d304f621c23c81580fbddaf61e61ef135558acd4
Submitter: Jenkins
Branch: master

commit d304f621c23c81580fbddaf61e61ef135558acd4
Author: wangxiyuan <email address hidden>
Date: Tue Mar 7 10:42:02 2017 +0800

    Don't change volume's status when create backups from snapshots

    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.
    When create a backup from a large snapshot, such as larger
    than 1 TB, it will cost few hours generally. It's really a
    problem that the volume is not available for such a long time.

    If the snapshot is provided, we change the status of the snapshot;
    otherwise, we change the status of the volume as usual.

    This patch added "backing-up" status for snapshot as well

    DocImpact

    Change-Id: I86d34c470fabbf4132b5e004d9f368e751c893a5
    Closes-bug: #1670541

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to cinder (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/451211

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to cinder (master)

Reviewed: https://review.openstack.org/451211
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=4b9233c7e5b46c8f6bcc5b41916310c77d04a5f7
Submitter: Jenkins
Branch: master

commit 4b9233c7e5b46c8f6bcc5b41916310c77d04a5f7
Author: wangxiyuan <email address hidden>
Date: Wed Mar 29 14:40:33 2017 +0800

    Fix error status check when create backup

    Now when creating backup from snapshot, the volume's status is
    still checked.

    This patch is a quick fix.

    Change-Id: I3a477ed622f076de9451741d198ac1d62c8d5b40
    Related-Bug: #1670541

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 11.0.0.0b1

This issue was fixed in the openstack/cinder 11.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers