Bug 1554013 - [RFE][Cinder] Support cross AZ backups
Summary: [RFE][Cinder] Support cross AZ backups
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M1
: 14.0 (Rocky)
Assignee: Gorka Eguileor
QA Contact: Avi Avraham
RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1649845 1650290 1650986 1650993
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-10 18:35 UTC by Christian Schwede (cschwede)
Modified: 2019-01-11 11:49 UTC (History)
7 users (show)

Fixed In Version: openstack-cinder-13.0.0-0.20180710093321.64bebcd.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:49:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 543463 0 'None' 'MERGED' 'Support cross AZ backups' 2019-11-14 17:17:53 UTC
OpenStack gerrit 543464 0 'None' 'MERGED' 'Support cross AZ backups' 2019-11-14 17:17:54 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:49:30 UTC

Description Christian Schwede (cschwede) 2018-03-10 18:35:27 UTC 
We currently limit backups to the same AZ of the volume while allowing volume restoration to any AZ. When having multiple AZs it is ideal to store your backups in a different AZ than the one where the source volumes are stored.
Comment 6 Avi Avraham 2018-11-21 14:54:27 UTC 
verified according to test plan 
RPM package list: 
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
Comment 10 errata-xmlrpc 2019-01-11 11:49:11 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/RHEA-2019:0045
Note You need to log in before you can comment on or make changes to this bug.