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 an bug with the handling of "True"/"true" by the cephadm mgr module when setting the config options. On Tue, Jul 18, 2023 at 11:38 AM Arnoud de Jonge <arnoud.dejonge@cyso.group> wrote:
Hi,
After having set up RadosGW with keystone authentication the cluster shows this warning:
# ceph health detail HEALTH_WARN Failed to set 1 option(s) [WRN] CEPHADM_FAILED_SET_OPTION: Failed to set 1 option(s) Failed to set rgw.fra option rgw_keystone_implicit_tenants: config set failed: error parsing value: 'True' is not one of the permitted values: false, true, swift, s3, both, 0, 1, none retval: -22
I might have made a typo but that has been corrected.
# ceph config dump |grep rgw_keystone_implicit_tenants client.rgw.fra.controller1.lushdc advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller1.pznmuf advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller1.tdrqot advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller2.ndxaet advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller2.rodqxh advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller2.wyhjuk advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller3.boasgr advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller3.lkczbl advanced rgw_keystone_implicit_tenants true * client.rgw.fra.controller3.qxctee advanced rgw_keystone_implicit_tenants true *
# ceph --version ceph version 17.2.6 (d7ff0d10654d2280e08f1ab989c7cdf3064446a5) quincy (stable)
Any idea on how to fix this issue?
Thanks, Arnoud. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io