-
Bug
-
Resolution: Won't Do
-
Minor
-
OADP 1.1.3
-
1
-
False
-
-
False
-
ToDo
-
-
-
Moderate
-
5
-
5.000
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem:
Restore of a RHEL 8 VM using VolSync and Restic fails to successfully restore the VM so that it can boot off the restored pvc. Backup has been taken using VolSync and Restic and stored to ODF MCG S3 based bucket (there were 3 warnings but flagged as successful). After removing the namespace and restoring the VM from backup, all resources are restored and the VM starts but is unable to find a bootable device.
Version-Release number of selected component (if applicable):
OCP 4.12.3
ODF 4.12.2
OADP 1.1.3
How reproducible:
Always
Steps to Reproduce:
1. Create DPA with VolSync but Restic enabled pointing to MCG S3 route of ODF
2. create a backup for a VM RHEL8
3. remove the VM and namespace containing the VM
4. restore namespace and VM from backup using a restore CR - it restores the namespace, and all related, including pvc, but VM fails on booting from the pvc based device
Actual results:
boot of the VM fails with "No bootable device"
Expected results:
VM should be able to boot off the restored pvc
Additional info:
log files and must-gather available:
- datamover-backup-vm9-1.tar.gz at https://drive.google.com/file/d/15_pF8lfBhn33C68L4dtO-RBhcLTtwZQz/view?usp=sharing
- datamover-backup-vm9-1-logs.gz at https://drive.google.com/file/d/1wO9AGrP57ZbLNQiStlPTqiT1und_z0z1/view?usp=sharing
- must-gather-VM-restore-failed-volsyncrestic-cephfs-202304271928.tar.gz at https://drive.google.com/file/d/1wyZDiXnjTSG1ygYs-rre5dzRs2m57c56/view?usp=sharing