Someone hit what I think is this same issue the other day. Do you have a
"config" section in your rgw spec that sets the
"rgw_keystone_implicit_tenants" option to "True" or "true"? For them,
changing the value to be 1 (which should be equivalent to "true" here)
instead of "true" fixed it. Likely
That is weird. As I had set it to ’true’ (lowercase) which is in the set of
permitted values. I have set it to 1 now, and it is accepted.
Thanks,
Arnoud.
> On 13 Jul 2023, at 15:32, Adam King wrote:
>
> The `config` section tells cephadm to try to set the given config options. So
> it will
The `config` section tells cephadm to try to set the given config options.
So it will try something equivalent to "ceph config set rgw.fra
rgw_keystone_implicit_tenants true" and what it reported in the health
warning "'True' is not one of the permitted values: false, true, swift, s3,
both, 0, 1,
Hi Adam,
That section is indeed pretty short. I’m not sure what the difference is
between the config and the spec section. Most of the settings I put under
config give an error when I put then under spec.
I have this spec now.
service_type: rgw
service_id: fra
placement:
label: rgw
Do you have a `config` section in your RGW spec? That health warning is
from cephadm trying to set options from a spec section like that. There's a
short bit about it at the top of
https://docs.ceph.com/en/latest/cephadm/services/#service-specification.
On Thu, Jul 13, 2023 at 3:39 AM wrote:
>
