cinder can't delete volume backup which has been created with container name
Bug #1623104 reported by
Alexander Gromov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
Medium
|
Alexander Gromov | ||
10.0.x |
Won't Fix
|
Medium
|
Alexander Gromov | ||
9.x |
Won't Fix
|
Medium
|
Alexander Gromov |
Bug Description
Configuration:
MOS 9.x Snapshot #251
Steps to reproduce:
1. Deploy environment with volume-ceph, ephemeral-ceph, image-ceph and rados-ceph
2. Go to controller node
3. Create volume
cinder create --image-id <image_id> --name Test_volume 1
4. Create volume backup with container name
cinder backup-create --container test_cont --name volume_backup <volume_id>
5. Try to delete created volume backup
Expected results:
Volume backup had 'available' status after step 4.
Volume backup was successfully deleted after step 5.
Actual result:
Volume backup had 'error' status after step 4.
Volume backup couldn't be deleted after step 5.
Changed in mos: | |
assignee: | nobody → MOS Cinder (mos-cinder) |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → 9.1 |
To post a comment you must log in.
Backup creation with an incorrect container name creates only DB record, no data affected. Also, nothing on backup storage is changed, so I propose to set priority to medium