Bug 1650993 - cinder attached volume backup failed when backup backend is in different availability zone
Summary: cinder attached volume backup failed when backup backend is in different avai...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Cinder Bugs List
QA Contact: Avi Avraham
Kim Nylander
URL:
Whiteboard:
Depends On:
Blocks: 1554013
TreeView+ depends on / blocked
 
Reported: 2018-11-18 15:25 UTC by Avi Avraham
Modified: 2018-11-21 16:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-21 16:22:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
cinder backup log file (14.11 KB, text/plain)
2018-11-18 15:25 UTC, Avi Avraham
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.