Bug 1358704

Summary: upgrade from 1.3.2 to 2.0 fails to convert old multisite configuration
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Orit Wasserman <owasserm>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: shilpa <smanjara>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.0CC: cbodley, ceph-eng-bugs, flucifre, hnallurv, kbader, kdreyer, mbenjamin, nlevine, owasserm, sweil, tmuthami, tserlin, vumrao
Target Milestone: rc   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.2-25.el7cp Ubuntu: ceph_10.2.2-20redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-15 11:17:01 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: 1363819    

Description Orit Wasserman 2016-07-21 10:06:52 UTC 
Description of problem:
Upgrade 1.3.2 with old multisite config (regions and zones) to 2.0 doesn't convert the old configuration correctly

Version-Release number of selected component (if applicable):


How reproducible:
Upgrade a 1.3.2 cluster with multisite config to 2.0

Steps to Reproduce:
1. Configure multisite on 1.3.2 (at least one region)
2. Upgrade to 2.0
3. check to configuration


Actual results:
radosgw-admin zone list is empty
radosgw-admin zonegroup list is empty
Expected results:
radosgw-admin zone list returns previous configured zones
radosgw-admin zonegroup returns list of previous configured regions

Additional info:
Comment 2 Orit Wasserman 2016-07-21 10:07:55 UTC 
upstream fix: https://github.com/ceph/ceph/pull/10368
Comment 3 Ken Dreyer (Red Hat) 2016-07-21 13:41:03 UTC 
Matt will cherry-pick this to ceph-2-rhel-patches today
Comment 19 errata-xmlrpc 2016-09-15 11:17:01 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://rhn.redhat.com/errata/RHBA-2016-1898.html