|
Thank You! I hope someone picks it up and fixes it. It does not appear to be a problem in Pacific (not sure about Octopus). We have a bunch of production systems that cannot upgrade very often.
The workaround is to put the rgw_frontend value in the ceph.conf file.
From: Casey Bodley <cbodley@xxxxxxxxxx>
Sent: Thursday, July 22, 2021 11:29 AM To: Wyll Ingersoll <wyllys.ingersoll@xxxxxxxxxxxxxx> Cc: dev@xxxxxxx <dev@xxxxxxx> Subject: Re: rados gw configuration parameters not being used this issue with rgw_frontends is tracked in
https://tracker.ceph.com/issues/50249, and was a regression related to RDMA work during nautilus. i haven't found any volunteers to work on this - if anyone is interested, please let me know On Thu, Jul 22, 2021 at 10:05 AM Wyll Ingersoll <wyllys.ingersoll@xxxxxxxxxxxxxx> wrote: > > > We're running RGW from Nautilus 14.2.21. We added configuration values for the radosgw client to the config db using "ceph config" and the values look as follows: > > client.radosgw.gw01 basic log_file /var/log/radosgw.log > client.radosgw.gw01 advanced rgw_dns_name gw01.ourdomain.com > client.radosgw.gw01 basic rgw_frontends beast ssl_endpoint=0.0.0.0 ssl_certificate=/etc/ceph/ssl/rgw.crt ssl_private_key=/etc/ceph/ssl/rgw.key > > However, when the radosgw is started it never sees any of these values and always starts with the default "beast port=7480" frontend. The keyring is in /etc/ceph/ceph.client.radosgw.keyring and is named appropriately with the right parameters and permissions. > > If I put the parameters in the RGW servers ceph.conf under "[client.radosgw.gw01]", they get used and it works as expected. > > We wanted to have a minimized ceph.conf and put everything else into the config DB, is this not possible in nautilus (for radosgw) ? > > Oddly enough, we have some slightly older nautilus based radosgw (14.2.15) on other hosts that have their settings all in the config DB and work fine. Wondering if there was a bug introduced in a later Nautilus build? > > thanks, > Wyllys Ingersoll > > > > > _______________________________________________ > Dev mailing list -- dev@xxxxxxx > To unsubscribe send an email to dev-leave@xxxxxxx |
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
