Bug #17239
closedradosgw-admin period update reverts deleted zonegroup
0%
Description
start the radosgw without any multisite configuration (default zonegroup and zone will be created)
create a realm , set it as default.
update zonegroup default and zone default using set commands
(this will cause the realm id to change)
update and commit the period
create a new master zonegroup zg0 and a new zg0zo that will the master of zg0
try to update the period, you will get an error as both zonegroups are master.
remove zone default from default zonegroup and delete it.
try period update
the same error and zonegroup default is part of the staging period
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
reproducible on current master
Updated by Casey Bodley over 7 years ago
- Related to Bug #16839: "default" zone and zonegroup cannot be added to a realm added
Updated by Orit Wasserman over 7 years ago
- Status changed from New to In Progress
- Assignee changed from Casey Bodley to Orit Wasserman
Updated by Orit Wasserman over 7 years ago
- Status changed from In Progress to Fix Under Review
- Backport changed from jewel to jewel,kraken
Updated by Yehuda Sadeh about 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #18712: jewel: radosgw-admin period update reverts deleted zonegroup added
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #18713: kraken: radosgw-admin period update reverts deleted zonegroup added
Updated by Nathan Cutler about 7 years ago
- Status changed from Pending Backport to Resolved