Re: 17.2.6 Dashboard/RGW Signature Mismatch

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

 



Le jeudi 13 avril 2023, 18:20:27 CEST Chris Palmer a écrit :
> Hi

Hello,

> I have 3 Ceph clusters, all configured similarly, which have been happy 
> for some months on 17.2.5:
> 
>  1. A test cluster
>  2. A small production cluster
>  3. A larger production cluster
> 
> All are debian 11 built from packages - no cephadm.
> 
> I upgraded (1) to 17.2.6 without any problems at all. In particular the 
> Object Gateway sections of the dashboard work as usual.
> 
> I then upgraded (2). Nothing seemed amiss, and everything seems to work 
> except... when I try to access the Object Gateway sections of the 
> dashboard I always get:
> 
> 
>       *The Object Gateway Service is not configured*
> 
> 
>         Error connecting to Object Gateway: RGW REST API failed request
>         with status code 403
>        
> (b'{"Code":"SignatureDoesNotMatch","RequestId":"tx0000022ba920e82ac4a9c-006
> 4381'
 b'934-10e73385-default","HostId":"10e73385-default-default"}') 
> (Just the RequestId changes each time). Before the upgrade it worked 
> just fine.

[...]

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



_______________________________________________
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