t such a problem so I wonder if this is
> something local to us - like perhaps I'm using "ceph config" incorrectly
> in a way which happened to be accepted before? Has anyone else seen this
> behavior?
>
> Graham
> --
> Graham Allan - g...@umn.edu
> Associate Director of
GPG: 4096R/A45477D5 |
> We all agree on the necessity of compromise. We just can't agree on
> when it's necessary to compromise. --Larry Wall
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
--
Arnaud Lefebvre
Clever Cloud
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
Hello,
I've been working on having SSE-S3 work too in the past few days with a v18
cluster (SSE-S3 is only available starting v17 IIRC).
First thing to check are the radosgw logs. Don't hesitate to increase them with
`debug rgw 20/20` if possible, you'll see the error and vault interactions.
