Activity log for bug #2007631

Date Who What changed Old value New value Message
2023-02-17 03:06:14 YuehuiLei bug added bug
2023-02-17 03:07:33 YuehuiLei 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 reasonable. 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. 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.
2023-02-17 08:53:36 OpenStack Infra cinder: status New In Progress
2023-02-17 12:27:58 Eric Harney cinder: importance Undecided High
2023-02-17 12:28:10 Eric Harney tags backup
2023-08-23 06:33:18 YuehuiLei cinder: assignee YuehuiLei (leiyuehui)