Description of problem:
In a multisite cluster, change the realm name on master zone and update the period. The change is not propagated to other zones
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure multisite with 3 zones in different clusters
2. Rename the realm name using 'realm rename' command and do a period update commit.
3. The change is not propagated to other zones.
Spoke to Casey and it appears to be an expected behaviour. Opening a BZ to discuss further.
This is the case because the realm name is not included in the period, and the period is the only information that gets shared between zones to keep their multisite configuration consistent.
The realm name could be added to the period to support this. When a zone gets a new period, it could update its local realm name accordingly (with care that its update doesn't race with another period).
Casey what is the next step with this bug? Do we plan to fix this in a PR, or is the current behavior expected?
I tend to agree with Orit that there isn't a good fix for this. I do think it's useful for admins to be able to rename their realms, so we should continue to support it. But the name itself is unused outside of these radosgw-admin commands, so we're unlikely to see any bugs caused by a mismatch in realm names between clusters.
My only recommendation is that we add some extra output to the 'radosgw-admin realm rename' command which instructs the admin to run that command on the other clusters as well.
cherry-picked changes to ceph-2-rhel-patches
FIx verified on ceph version 10.2.7-13.el7cp (4955aa6a90abc27bc043729db19df24e1c840eac)
radosgw-admin realm rename --rgw-realm studs --realm-new-name=movs --cluster master
Realm name updated. Note that this change only applies to the current cluster, so this command must be run separately on each of the realm's other clusters.
Mopving to verified.
I've updated the Doc Text field to reflect the fix so that it can be included in the Release Notes as a bug fix.
Could you check out the text and let me know if you think it is sufficient?
Looks great Erin, thanks.
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.