Created attachment 1277080 [details] evm log while reproducing backup issue Description of problem: For attached that in used backup unable to create an incremental backup for an 'in-use' volume. Error recieved: Unable to create backup for Cloud Volume "yyy": uninitialized constant MiqException::MiqVolumeBackupCreateError Version-Release number of selected component (if applicable): 5.8.0.13 How reproducible: most likely Steps to Reproduce: 1. Create a 1 GB volume and attached it to an instance 2. Browse to: storage --> Volumes 3. Select the volume which created on step 1 4. Click configuration, and select Back-up selected Cloud Volumes Volume backup wizard 5. On volume backup wizard Enter name and select incremental backup Actual results: Failed to create a backup with error: Unable to create backup for Cloud Volume "yyy": uninitialized constant MiqException::MiqVolumeBackupCreateError Expected results: Volume backup created successfully list of volume back up should update Additional info:
Created attachment 1277101 [details] evm log from restore from backup failure
It looks like we're just missing the appropriate exception wrapping, but the correct API call is going through; for example, the real restore-from-backup error in the log is: "Invalid volume: Volume to be restored to must be available"
Able to create volume backup from CLI [stack@undercloud-0 ~]$ cinder backup-create vol1 --name osp_backup +-----------+--------------------------------------+ | Property | Value | +-----------+--------------------------------------+ | id | 20ea038e-b8a3-4519-ba17-a4a4d92cd65d | | name | osp_backup | | volume_id | e8e29ee2-adb4-4c2a-849e-80ff63f182cd | +-----------+--------------------------------------+
Fixed by https://github.com/ManageIQ/manageiq-gems-pending/pull/205 I believe.
Verified ======== 5.9.0.20
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, 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/RHSA-2018:0380