Right, I almost forgot that one, I stumbled upon the performance
regression as well. :-/
Zitat von Michel Jouvin <michel.jou...@ijclab.in2p3.fr>:
Thanks for these answers, I was not able to find information
mentioning the problem, thus my email. I didn't try 16.2.11 because
of the big mentioned by others in volume activation when using
cephadm.
Michel
Sent from my mobile
Le 11 avril 2023 22:28:37 Eugen Block <ebl...@nde.ag> a écrit :
Hi,
version 16.2.11 (which was just recently released) contains a fix for
that. But it still doesn’t work with wildcard certificates, that’s
still an issue for us.
Zitat von Michel Jouvin <michel.jou...@ijclab.in2p3.fr>:
Hi,
Our cluster is running Pacific 16.2.10. We have a problem using the
dashboard to display information about RGWs configured in the
cluster. When clicking on "Object Gateway", we get an error 500.
Looking in the mgr logs, I found that the problem is that the RGW is
accessed by its IP address rather than its name. As the RGW has SSL
enabled, the certificate cannot be matched against the IP address.
I digged into the configuration but I was not able to identify where
an IP address rather than a name was used (I checked in particular
the zonegroup parameters and names are used to define endpoints).
Did I make something wrong in the configuration or is it a know
issue when using SSL-enabled RGW?
Best regards,
Michel
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
