Bug 1650993

Summary: cinder attached volume backup failed when backup backend is in different availability zone
Product: Red Hat OpenStack Reporter: Avi Avraham <aavraham>
Component: openstack-cinderAssignee: Cinder Bugs List <cinder-bugs>
Status: CLOSED WORKSFORME QA Contact: Avi Avraham <aavraham>
Severity: unspecified Docs Contact: Kim Nylander <knylande>
Priority: unspecified    
Version: 14.0 (Rocky)CC: aavraham, abishop, cschwede, geguileo, tshefi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-21 16:22:33 UTC Type: Bug
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:    
Bug Blocks: 1554013    
Attachments:
Description Flags
cinder backup log file none

Description Avi Avraham 2018-11-18 15:25:02 UTC
Created attachment 1506961 [details]
cinder backup log file

Description of problem:
backup end with error state While trying to backup attached volume with --force flag when backup backend is in different availability zone.

Version-Release number of selected component (if applicable):
python-cinder-13.0.1-0.20181013185427.31ff628.el7ost.noarch
python2-cinderclient-4.0.1-0.20180809133302.460229c.el7ost.noarch
puppet-cinder-13.3.1-0.20181013114719.25b1ba3.el7ost.noarch
openstack-cinder-13.0.1-0.20181013185427.31ff628.el7ost.noarch

How reproducible:


Steps to Reproduce:
1. setup cinder backup 
2. configure backend in different AZ then backup backend  
3. create volume from image.
4. attach volume to instance 
5. run the following command to run a backup:
cinder backup-create --name vol-cirros-backup1 --availability-zone nova --force vol-cirros

Actual results:
backup finished in error state
+--------------------------------------+--------------------------------------+-----------+--------------------+------+--------------+-----------+
| ID                                   | Volume ID                            | Status    | Name               | Size | Object Count | Container |
+--------------------------------------+--------------------------------------+-----------+--------------------+------+--------------+-----------+
| 0d17374d-6c68-4b45-84a2-754c6d72754d | c3ede874-a327-4205-8a4f-cf340f1930e1 | error     | vol-cirros-backup1 | 1    | 0            | -         |
| c9a1444b-35e2-4e90-820b-bbec466867a1 | c3ede874-a327-4205-8a4f-cf340f1930e1 | available | vol-cirros-backup  | 1    | 0            | backups   |
+--------------------------------------+--------------------------------------+-----------+--------------------+------+--------------+-----------+

Expected results:
backup ends in "available" state

Additional info:
log attached

Comment 4 Alan Bishop 2018-11-21 16:22:33 UTC
The problem was caused by a known bug in the NFS backend. The problem was not observed when testing with a different backend.