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 count_per_host: 3 networks: - 10.103.4.0/24 config: rgw enable usage log: true rgw keystone accepted roles: Member, _member_, admin rgw keystone admin domain: default rgw keystone admin password: secret rgw keystone admin project: service rgw keystone admin user: swift rgw keystone api version: 3 rgw keystone implicit tenants: true rgw keystone url: http://10.103.4.254:35357 rgw s3 auth use keystone: true rgw swift account in url: true rgw usage log flush threshold: 1024 rgw usage log tick interval: 30 rgw usage max shards: 32 rgw usage max user shards: 1 spec: rgw_frontend_port: 8100 I deleted the 'rgw keystone implicit tenants’ settings now, and the warning disappeared. Seems like it has been deprecated? The warning message is very misleading. Thanks, Arnoud. > On 13 Jul 2023, at 14:07, Adam King <adking@xxxxxxxxxx> wrote: > > 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 <arnoud@fuga.cloud <mailto:arnoud@fuga.cloud>> 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. >> >> >> -- >> Arnoud de Jonge >> DevOps Engineer >> >> FUGA | CLOUD >> https://fuga.cloud <https://fuga.cloud/> <https://fuga.cloud/> >> arnoud@fuga.cloud <mailto:arnoud@fuga.cloud> <mailto:arnoud@fuga.cloud <mailto:arnoud@fuga.cloud>> >> >> Phone +31727513408 <tel://+31727513408> >> Registration ID 64988767 >> VAT ID NL855935984B01 >> Twitter @fugacloud >> >> _______________________________________________ >> ceph-users mailing list -- ceph-users@xxxxxxx <mailto:ceph-users@xxxxxxx> >> To unsubscribe send an email to ceph-users-leave@xxxxxxx <mailto:ceph-users-leave@xxxxxxx> _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |