Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2188051

Summary: [16.2]: Cinder backup with ceph backup driver could not restore a volume other than ceph
Product: Red Hat OpenStack Reporter: alisci <alisci>
Component: openstack-cinderAssignee: Cinder Bugs List <cinder-bugs>
Status: CLOSED ERRATA QA Contact: Luigi Toscano <ltoscano>
Severity: high Docs Contact: RHOS Documentation Team <rhos-docs>
Priority: high    
Version: 16.2 (Train)CC: astupnik, brian.rosmaita, eshames, geguileo, gfidente, hfukumot, ifrangs, jamsmith, jfindysz, jveiraca, kgilliga, kkawakami-je, knoha, ltoscano, mariel, mburns, redhat-bz, rhel-osp-bz, udesale, vhariria
Target Milestone: z6Keywords: Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-cinder-15.6.1-2.20230906144855.el8ost Doc Type: Bug Fix
Doc Text:
Before this update, the Block Storage (cinder) Ceph backup driver did not form the internal backup name correctly. As a result, backups that were stored in Ceph could not be restored to volumes that were stored on a non-Ceph backend. With this update, the Red Hat Ceph Storage backup driver forms backup names correctly. Ceph can now identify all the constituent parts of a backup and can restore the data to a volume that is stored on a non-Ceph backend.
Story Points: ---
Clone Of: 1847905
: 2231378 (view as bug list) Environment:
Last Closed: 2023-11-08 19:18:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2231378    
Bug Blocks: 1847905    

Comment 4 Sofia Enriquez 2023-04-26 11:02:44 UTC
Hi Andrea, hope you are doing fine,

I'm seeing in the customer case a base name `volume-<vol-uuid>.backup.base`. On the description says that the steps to reproduce are: 1.cinder backup-create <unattached volume uuid from NFS backend> and 2.cinder backup-restore <created back uuid> --name <testrestoredvolume> . However, just to double check:

Do you know if the backup was created from a Cinder snapshot? (i.e. using: cinder backup-create <volume-uuid> --snapshot-id <snapshot-uuid>)

Cheers,

Sofia

Comment 24 Brian Rosmaita 2023-10-03 19:34:32 UTC
Setting fixed-in version to openstack-cinder-15.6.1-2.20231003174841.299553a.el8osttrunk , which is tagged 'rhos-16.2-rhel-8-trunk-candidate':
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2702948

Comment 30 Luigi Toscano 2023-10-18 16:53:11 UTC
Tested according the instruction of the original bug:


h) Steps to Reproduce: 
   1. Setup the cinder backup driver to 'cinder.backup.drivers.ceph.CephBackupDriver'

      backup_driver=cinder.backup.drivers.ceph.CephBackupDriver

   2. Create 'LVM' volume.

     $ cinder create --volume-type lvm --name "lvm_vol" 1

   3. Create backup from 'LVM' volume.

     $ cinder backup-create lvm_vol --name "backup_from_lvm_vol" 

   4. Create 'LVM' volume to restore the backup.

     $ cinder create --volume-type lvm --name "restore_backup_lvm" 1

   5. Restore from the backup to 4) volume.

     $ cinder backup-restore backup_from_lvm_vol --volume restore_backup_lvm

It was tested with LVM/iSCSI, as the fix really depends on the ceph backup driver, not on the driver of the source/destination volume.

The above steps now works.

openstack-cinder-15.6.1-2.20230906144855.el8ost.noarch
python3-cinderclient-5.0.2-2.20220107174846.7e9e31c.el8ost.noarch

Comment 32 Brian Rosmaita 2023-10-18 17:10:41 UTC
Added suggested doc text.

Comment 40 errata-xmlrpc 2023-11-08 19:18:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.2.6 (Train) bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6307