[RBD] Volume status becomes available after force delete
Bug #1959350 reported by
ZhaoYixin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Incomplete
|
Low
|
Unassigned | ||
Bug Description
To restore a volume (rbd) through backup, the status of the volume is restoring-backup.
At this time, force delete the volume, and the status of the volume becomes available, but the restore process is still in progress.
Steps to reproduce:
> restore backup
openstack volume backup restore <backup_id> <volume_id>
> force delete volume
openstack volume delete <volume_id> --force
> show volume
openstack volume show <volume_id>
| summary: |
- Volume status becomes available after force delete + [RBD] Volume status becomes available after force delete |
Revision history for this message
| Sofia Enriquez (lsofia-enriquez) wrote | #1 |
| tags: | added: backup-service rdb |
| Changed in cinder: | |
| importance: | Undecided → Medium |
| status: | New → Incomplete |
| Changed in cinder: | |
| importance: | Medium → Low |
To post a comment you must log in.
Greetings ZhaoYixin,
- are you facing this issue on master?
- Would you mind sharing the expected output you are waiting for? I think this isn't a bug... as the status is 'restoring' cinder ignores the delete call. However, It should show a warning or something when ignoring the delete call so the user doesn't wait for it.
Best Regards,
Sofia