Description of problem: try the same error and zonegroup default is part of the staging period Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.start the radosgw without any multisite configuration (default zonegroup and zone will be created) 2.create a realm , set it as default. 3.update zonegroup default and zone default using set commands (this will cause the realm id to change) 4. update and commit the period 5. create a new master zonegroup zg0 and a new zg0zo that will the master of zg0 6. radosgw-admin period update --commit (error two master zonegroups) 7. remove zone default from default zonegroup and delete it 8. period update Actual results: error two master zonegroups and zonegroup default is part of the staging period Expected results: success Additional info: workround: delete .rgw.root: rados purge .rgw.root --yes-i-really-really-mean-it create a new configuration when the gateway is down: create a new realm and set it as default radosgw-admin zonegroup set < json (with the new realm id) radosgw-admin zoneg set < json (with the new realm id) set zonegroup and zone as default period update --commit
@cbodley, @owasserm assigning to ensure backport
(In reply to Matt Benjamin (redhat) from comment #4) > @cbodley, @owasserm assigning to ensure backport It is part of Jewel 10.2.7, no need to backport
Verified on ceph-radosgw-10.2.7-13
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/RHBA-2017:1497