Volume State Update Failed After Backup Completed

[wanghelin]

Generally, after the backup is created, the state of the volume will be reset to the state before the backup. However, if we create a backup of a volume with status 'in-use'(attached to an instance). When backup creating, the instance get deleted, status will be set to in-use by error, but not reset to available.

When an instance is deleted, the volume will be detached, and the volume status will be set to available. After that, the volume backup is completed, and the status of the volume is reset to in-use. The bug is caused by this.

[Sofia Enriquez (lsofia-enriquez)]

Hi Wanghelin, thanks for reporting this bug.
Would you mind sharing the cinder version you are referring to?
In addition to that, would you mind sharing the backend you are using?
Thanks in advanceSofia

[Sofia Enriquez (lsofia-enriquez)]

Please read meeting notes regarding this bug https://meetings.opendev.org/meetings/cinder_bs/2022/cinder_bs.2022-11-09-15.00.log.html#l-70

[Christian Rohmann (christian-rohmann)]

Sofia, may I bluntly bring up the idea and pending spec of externalizing the backup status to a dedicated field again (see: https://review.opendev.org/c/openstack/cinder-specs/+/818551/comments/6ade3ca0_d95e489d)?

I shall place this as a topic for a Cinder Weekly meeting again. Would love to see the backup status, which is usually independent from the actual volume status, more decoupled.

[Sofia Enriquez (lsofia-enriquez)]

Thanks Christian Rohmann.
This bug is related to:
https://blueprints.launchpad.net/cinder/+spec/move-task-status-to-dedicated-field

[Sofia Enriquez (lsofia-enriquez)]

More context: https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-11-23-14.00.log.html#l-61

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/866106