Re: Pacific dashboard: unable to get RGW information

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It feels like removing the option to set the rgw api host (in previous releases 'ceph dashboard set-rgw-api-host') is a regression. Apparently, there are many use-cases not covered by the automatic setting. I don't know the reasons behind the decision to implement it that way, but maybe it's worth looking at it again?

Zitat von Gilles Mocellin <gilles.mocellin@xxxxxxxxxxxxxx>:

I forgot, there's a similar bug around that :
https://tracker.ceph.com/issues/58811

Le mardi 11 avril 2023, 22:45:28 CEST Gilles Mocellin a écrit :
Hi,

My problem is the opposite !
I don't use SSL on RGWs, because I use a load balancer with HTTPS endpoint.
so no problem with certificates and IP adresses.
With 16.2.11, it does not work anymore because it uses DNS names, and those

 names are resolving to a management IP, which is not the network where I
expose the RGWs...

So for everyone to have a working dashboard, we need to be able to override

 that configuration, and set what ever we want as RGW endpoints.

PS: I still don't use cephadm, but ceph-ansible. Perhaps things are
different
 with containers.

Le mardi 11 avril 2023, 22:26:28 CEST Eugen Block 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.jouvin@xxxxxxxxxxxxxxx>:
>
>
>
> > 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@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



_______________________________________________
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




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux