Mirantis OpenStack

cinder can't delete volume backup which has been created with container name

Bug #1623104 reported by Alexander Gromov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
Medium
Alexander Gromov
Mirantis OpenStack 9.2
10.0.x
Won't Fix
Medium
Alexander Gromov
Mirantis OpenStack 10.0
9.x
Won't Fix
Medium
Alexander Gromov
Mirantis OpenStack 9.2

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.

Tags: move-to-9.2
Revision history for this message
Alexander Gromov (agromov) wrote :
Timur Nurlygayanov (tnurlygayanov)
Changed in mos:
assignee: nobody → MOS Cinder (mos-cinder)
importance: Undecided → High
status: New → Confirmed
milestone: none → 9.1
Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

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

tags: added: move-to-9.2
Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Let me clarify what I mean saying 'incorrect container name':

For Ceph-based deployment, Cinder backup container it is a Ceph pool. By default, MOS deploys Ceph with two containers: volumes and backups. Cinder can't create new pools in Ceph. Pool creation should be done in scope of deployment or post-deployment configuration. So for Cinder backup you should pass real Ceph pool name ('backups' will be used by default) and Cinder user should have r/w permissions.

Revision history for this message
Michael Dovgal (mdovgal) wrote :

I reproduced this situation and as Ivan has told earlier, cinder can't create backup in container with invalid name (except volumes and backups) because it just can't find where to create it. That's why backup's state will be 'error' when you run cinder backup-list and it's normal behavior.
And you can't delete it from the backup's list.

Changed in mos:
assignee: Michael Dovgal (mdovgal) → Alexander Gromov (agromov)
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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