Bug #16839
closed"default" zone and zonegroup cannot be added to a realm
0%
Description
Radosgw creates a zone and zonegroup by default, but does not create a default realm. The default zone and zonegroup are both created with an empty "realm_id" field.
If a realm is later created, the 'radosgw-admin period update' command will reject the default zone and zonegroup because their "realm_id" does not match the realm's. This makes it difficult to add a multisite configuration to a cluster with existing data in the "default" pools. You have to manually edit the zone's json format to either: a) change the default zone's realm_id, or b) change a new zone's pool names to match the existing "default.rgw.*" pools.
My suggestion would be to create a realm by default and associate it with the default zone and zonegroup, so that realm could be extended later to include more zones or zonegroups.
Updated by Orit Wasserman over 7 years ago
Creating a default realm will have backward compatibility issue as it doesn't exists in jewel.
How about using zonegroup modify and zone modify commands to update the realm id?
Updated by Casey Bodley over 7 years ago
- Backport set to jewel
Orit Wasserman wrote:
Creating a default realm will have backward compatibility issue as it doesn't exists in jewel.
How about using zonegroup modify and zone modify commands to update the realm id?
good idea! https://github.com/ceph/ceph/pull/10477
Updated by Casey Bodley over 7 years ago
- Status changed from New to Pending Backport
Updated by Nathan Cutler over 7 years ago
- Copied to Backport #16862: jewel: "default" zone and zonegroup cannot be added to a realm added
Updated by Loïc Dachary over 7 years ago
- Status changed from Pending Backport to Resolved
Updated by Casey Bodley over 7 years ago
- Related to Bug #17239: radosgw-admin period update reverts deleted zonegroup added