Cinder

Volumes stays in '-ing' state after back-create call if backup service is unavailable

Bug #1896087 reported by Ivan Kolodyazhny
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Ivan Kolodyazhny

Bug Description

Steps to reproduce:

1. Create volume
2. Stop cinder-backup if it's up and running
3. Try to create backup

Expected results:
1. Backup is in 'error' state
2. Volume is in 'available' state

Actual result:
Volume is in 'backing-up' state

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

Fix proposed to branch: master
Review: https://review.opendev.org/752497

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

Reviewed: https://review.opendev.org/752497
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9744849712531f0385ca5b99cc1b9294e6d14b54
Submitter: Zuul
Branch: master

commit 9744849712531f0385ca5b99cc1b9294e6d14b54
Author: Ivan Kolodyazhny <email address hidden>
Date: Thu Sep 17 19:14:22 2020 +0300

    Rollback volume status if backup service is unavailable

    We should not keep volume in 'backing-up' state if backup creation
    process failed. It should be reverted to the previous state.

    Change-Id: I33d4569df439fa59dec847f8dbc9f516a4839070
    Closes-Bug: #1896087

Changed in cinder:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.