Boris, et al: What this appears to mean is that the rgw_sigv4_insecure option does not exist in releases prior to 19.2.6/20.2.4, but using 'force' sets it anyway, so that when a 19.2.6 or 20.2.4 version of radosgw starts, it will see it and use it. I suspect that if a 19.2.6 or 20.2.4 radosgw starts without this option it will fail to do replication to say an earlier radosgw without the signature fix on the other side of a multisite that has not yet updated. As we always have, we plan on doing the update on one side of the multisite on day 1, and the other side on day 2. The force option seems to make this possible without having to modify ceph.conf everywhere. If I am wrong, please someone correct me. Thanks. -ChrisOn Tuesday, August 25, 2026 at 01:49:30 AM MDT, Boris <bb@kervyn.de> wrote: Hi Matthew, we've set it with: ceph config set client.rgw rgw_sigv4_insecure true --force Best Boris Am Di., 25. Aug. 2026 um 09:41 Uhr schrieb Matthew Vernon <ceph-users@ceph.io>:
Hi,
On 19/08/2026 17:09, Patrick Donnelly wrote:
If you are running multisite, you must set the ``rgw_sigv4_insecure`` option to true before you begin to upgrade. After all clusters are upgraded, set the option to ``false`` again.
Stupid question - how/where does one set this, and will this be understood by older versions of Ceph?
I ask because I have a Reef multisite setup, which should be supported to upgrade to Tentacle. Which I fear I'm now going to have to do in a hurry!
AFAICT this is a new config setting, so I'd expect older versions of Ceph won't understand it... [and searching the reef docs doesn't find it]
Thanks,
Matthew _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im groüen Saal. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io