Bug 1448827

Summary: Unable to create incremental backup of cloud volume for attached volume
Product: Red Hat CloudForms Management Engine Reporter: Ronnie Rasouli <rrasouli>
Component: ProvidersAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: iovadia, jfrey, jhardy, obarenbo, simaishi, slucidi, tzumainn
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack:volume:backup
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:12:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Embargoed:
Attachments:
Description Flags
evm log while reproducing backup issue
none
evm log from restore from backup failure none

Description Ronnie Rasouli 2017-05-08 10:17:18 UTC
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:

Comment 3 Ronnie Rasouli 2017-05-08 13:24:05 UTC
Created attachment 1277101 [details]
evm log from restore from backup failure

Comment 4 Tzu-Mainn Chen 2017-05-08 13:46:17 UTC
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"

Comment 5 Ronnie Rasouli 2017-05-14 06:50:39 UTC
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 |
+-----------+--------------------------------------+

Comment 8 Sam Lucidi 2017-11-15 20:35:38 UTC
Fixed by https://github.com/ManageIQ/manageiq-gems-pending/pull/205 I believe.

Comment 9 Ido Ovadia 2018-02-15 14:17:17 UTC
Verified
========
5.9.0.20

Comment 12 errata-xmlrpc 2018-03-01 13:12:35 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, 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