Bug #24348
closed
rgw (luminous) making implicit_tenants backwards compatible.
Added by Marcus Watts almost 6 years ago.
Updated about 4 years ago.
Backport:
nautilus mimic luminous
Description
In jewel, "rgw keystone implicit tenants" only applied to swift. In luminous(,+), it applies to s3 also. Sites that used this feature with jewel now have outstanding data that depends on the old behavior. One proposal to fix this was to expand this option so that it can be set to "none", "all", "s3" or "swift".
I've made a PR that I beleive will address this.
https://github.com/ceph/ceph/pull/22363
this is for luminous: I'll need to make what should be a very similar PR for master.
The main complication is that it turns out the code that was in luminous only looked at "rgw keystone implicit tenants" when creating a new shadow user. With this PR, it look at that first to see if it's operating in "split mode" (implicit tenants only enabled for one protocol), and if so, only looks for the kind of shadow user that it would otherwise create.
- Status changed from New to Fix Under Review
- Backport set to mimic, luminous
- Copied to Backport #24393: luminous: rgw: making implicit_tenants backwards compatible added
- Status changed from Fix Under Review to Pending Backport
- Backport changed from mimic, luminous to nautilus mimic
- Copied to Backport #44444: nautilus: rgw (luminous) making implicit_tenants backwards compatible. added
- Copied to Backport #44445: mimic: rgw (luminous) making implicit_tenants backwards compatible. added
- Backport changed from nautilus mimic to nautilus mimic luminous
ERROR:root:https://tracker.ceph.com/issues/24348 has more backport issues (luminous,mimic,nautilus) than expected (mimic,nautilus)
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF