Hello Robin,
thank you.
The object-stat did not show anything suspicious.
And the logs do show
s3:get_obj decode_policy Read AccessControlPolicy<AccessControlPolicy
xmlns="http://s3.amazonaws.com/doc/2006-03-01/";><Owner><ID>XXXXX</ID><DisplayName>YYYYY
</DisplayName></Owner><AccessControlList><Grant><Grantee
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="CanonicalUser"><ID>XXXXX</ID><DisplayName>YYYYY
</DisplayName></Grantee><Permission>FULL_CONTROL</Permission></Grant></AccessControlList></AccessControlPolicy
and than it fails with
s3:put_obj http status=403
So we do not see any errors or something.
Everything looks the same to the other working buckets.
No versioning.
But there has to be something.
Where can I have a look?
I tried almost anything with the aws cli to find something. But there is
nothing.
Are there any rados or other commands to debug this?
Best,
Malte
On 22.03.24 02:35, Robin H. Johnson wrote:
On Thu, Mar 21, 2024 at 11:20:44AM +0100, Malte Stroem wrote:
Hello Robin,
thanks a lot.
Yes, I set debug to debug_rgw=20 & debug_ms=1.
It's that 403 I always get.
There is no versioning enabled.
There is a lifecycle policy for removing the files after one day.
Did the object stat call return anything?
Can you show more of the debug output (redact the keys/hostname/filename)?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
