Replies: 4 comments 3 replies
-
I've never seen this particular message from The first thing to do is make sure that the version of Ceph inside the If the version is lower in the operator pod, you will have to update the Rook version used. |
Beta Was this translation helpful? Give feedback.
-
This error is not from the The Accessing http://radosgw.api S3 API or http://radosgw.api/swift/v1 API works fine using the keystone credentials. Could it be the result of using the keystone for the auth?
|
Beta Was this translation helpful? Give feedback.
-
UPD: I updated the keystone override config and changed I was sure that oncev the Keystone auth doesn't work, Rados must fallback to the internal auth. Isn't this true anymore? UPD2: I set the How can I enable both auth? Is there a fallback option that I'm not aware of? UPD3: I set the config section to UPD4: I enabled debug logs with the global's
with the keystone disabled:
So it looks like the keystone auth disables the |
Beta Was this translation helpful? Give feedback.
-
I discovered the |
Beta Was this translation helpful? Give feedback.
-
I'm getting
failed to reconcile CephObjectStore rook-ceph/ceph-objectstore-st1-default. failed to create object store deployments: failed to get COSI user cosi: SignatureDoesNotMatch tx00000caa4f7677e4cdac4-0066438484-9cced-ceph-objectstore-st1-default 9cced-ceph-objectstore-st1-default-ceph-objectstore-st1-default
while creating an objectstore.Here is my cephobjectstore resource:
and the config-override:
accessing S3 and Swift API works fine, the problem is only for
cosi
user. I also created a small script that tries to retrieve acosi
user using the credentials returned by theradosgw-admin user info --uid rgw-admin-ops-user | jq -r '.keys[]'
, but it still returnsSignatureDoesNotMatch
.CEPH version: v18.2.2
Please advice.
Beta Was this translation helpful? Give feedback.
All reactions