Hi,
For what is worth, we have a similar problem in 16..2.10 that I had no time
to troubleshoot yet. It happened after adding a haproxy in front of rgw to
manage https and switch rgw to http (to overcome the other pb mentioned
when using https in rgw). The access/secret key is refused despite it
matches the dashboard user.
Best regards,
Michel
Sent from my mobile
Le 13 avril 2023 19:26:00 Chris Palmer <chris.palmer@xxxxxxxxx> a écrit :
On 13/04/2023 18:15, Gilles Mocellin wrote:
I suspect the same origin of our problem in 16.2.11, see Tuesday's thread
" Pacific dashboard: unable to get RGW information".
https://www.mail-archive.com/ceph-users%40ceph.io/msg19566.html
Unfortunately I don't think it is the same problem. We are not using TLS
into the RGW instances. They are fronted by an HAProxy instance that
provides the TLS termination and load-balancing. Tcpdump shows the
connections are fine, and the error is a 403 (denied) along with the
text indicating the signature problem. And we have the same setup on
both clusters (1) and (2) yet only (2) is failing...
Thanks for the reference though.
Chris
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
