Description of problem: put-bucket-logging with target being the same bucket in the policy is not denied. and log objects also delivered to the same bucket [root@magna016 ~]# aws --endpoint-url http://10.8.128.16:81 --profile hsm s3api put-bucket-logging --bucket src-bkt1 --bucket-logging-status file://logging.json [root@magna016 ~]# [root@magna016 ~]# aws --endpoint-url http://10.8.128.16:81 --profile hsm s3api get-bucket-logging --bucket src-bkt1 { "LoggingEnabled": { "TargetBucket": "src-bkt1", "TargetPrefix": "src-bkt1-logs/", "TargetObjectKeyFormat": { "PartitionedPrefix": { "PartitionDateSource": "DeliveryTime" } } } } [root@magna016 ~]# Version-Release number of selected component (if applicable): ceph version 19.2.0-19.el9cp How reproducible: always Steps to Reproduce: 1.deploy rhcs8.0 with rgw daemon 2.create a bucket 3.put-bucket-logging on the bucket with TargetBucket as the same bucket in the policy. it is not denying the request Actual results: put-bucket-logging with target being the same bucket is allowed. Expected results: put-bucket-logging with target being the same bucket should be denied. Additional info: https://docs.google.com/document/d/1R9Qol5tNXwNXFQJLpagUdBSyNp7U11YJR67aym_thvg/edit?tab=t.0#heading=h.bkxdrlysjrzd
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat Ceph Storage 8.1 security, bug fix, and enhancement updates), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2025:9775