Bug 1423886
Summary: | In a multisite env, realm rename does not get updated to other zones | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | shilpa <smanjara> |
Component: | RGW | Assignee: | Casey Bodley <cbodley> |
Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
Severity: | medium | Docs Contact: | Erin Donnelly <edonnell> |
Priority: | unspecified | ||
Version: | 2.2 | CC: | cbodley, ceph-eng-bugs, edonnell, hnallurv, kbader, kdreyer, mbenjamin, owasserm, sweil, uboppana |
Target Milestone: | rc | ||
Target Release: | 2.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-10.2.7-12.el7cp Ubuntu: ceph_10.2.7-14redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.The output of the `radosgw-admin realm rename` command now alerts the administrator to run the command separately on each of the realm's clusters
In a multi-site configuration, the name of a realm is only stored locally and is not shared as part of the period. As a consequence, when it is changed on one cluster, the name is not updated on the other cluster. Previously, users could easily miss this step, which could lead to confusion. With this update, the output of the `radosgw-admin realm rename` command contains instructions to rename the realm on other clusters as well.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-19 13:29:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1412948, 1437916 |
Description
shilpa
2017-02-17 15:06:48 UTC
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? Hi Ken, 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. Hi Casey, 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? Thanks, Erin 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. https://access.redhat.com/errata/RHBA-2017:1497 |