When creating a backup fails, the volume status is changed to None

Bug #2007631 reported by YuehuiLei
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
In Progress
High
YuehuiLei

Bug Description

After the backup service is down,use the following body to create a backup:
{
    "backup": {
        "container": null,
        "description": null,
        "name": "backup001",
        "volume_id": "64f5d2fb-d836-4063-b7e2-544d5c1ff607",
        "snapshot_id": "64h8d5fb-d096-4098-n8y9-j998sj8dh6tg5",
    }
}
Backup failure is normal. But the volume status has been changed to None, which is problematic.

When there is a "snapshot_id" field in the body, it should be the backup created based on the snapshot. The snapshot status should be changed, and the volume status should not be changed.

Tags: backup
YuehuiLei (leiyuehui)
description: updated
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/c/openstack/cinder/+/873862

Changed in cinder:
status: New → In Progress
Eric Harney (eharney)
Changed in cinder:
importance: Undecided → High
tags: added: backup
YuehuiLei (leiyuehui)
Changed in cinder:
assignee: nobody → YuehuiLei (leiyuehui)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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