.ceph-radosgw starts as expected after upgrading from 1.3 to 2 when a non-default value is used for rgw_region_root_pool and rgw_zone_root_pool
Previously, the `ceph-radosgw` service did not start after upgrading the Ceph Object Gateway from 1.3 to 2, when the Gateway used non-default values for the `rgw_region_root_pool` and `rgw_zone_root_pool` parameters. This bug has been fixed and the `ceph-radosgw` now starts as expected.
upstream fix: https://github.com/ceph/ceph/pull/12076
If the rgw_region_root_pool and rgw_zone_root_pool are the same, we have a simple workaround:
The user need to add rgw_zonegroup_root_pool (rgw zonegroup root pool) to his configuration with the same value as rgw_region_root_pool.
For the workaround:
The user should also set rgw_realm_root_pool and rgw_period_root_pool.
Orit, would you please check Loic's backport to jewel upstream and approve it
if it properly fixes this issue?
(In reply to Ken Dreyer (Red Hat) from comment #5)
> Orit, would you please check Loic's backport to jewel upstream and approve it
> if it properly fixes this issue?
The backport looks good but it still needs an additional config change for succefull upgrade. I added a known issue
Created attachment 1281409 [details]
discussed at program meeting, development believes what QE is seeing is not a bug. Harish believe credentials to this machine are the "usual". will investigate today.
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.