Description of problem: Object download fails after restoration via "aws s3api restore-object", when read_through option was disabled during upload Despite the successful completion of the restore operation, attempts to download the restored object fail, resulting in errors. This issue impacts the accessibility of archived/cloud-tiered objects that were uploaded without the read_through option enabled or was not available (in Upgraded Environments.) Version-Release number of selected component (if applicable): ceph version 19.1.0-67.el9cp How reproducible: Always Steps to Reproduce: 1. With read_through option = false or not available, transition an object to the cloud. 2. Try to restore the object via the was s3api restore-object cli. aws --endpoint http://ceph-pri-vim-ms-8-0-glw3l4-node4:80 s3api restore-object --bucket testaws1 --key file-aws-20 --restore-request Days=10 3. Once the object is restored, try to download the object. # s3cmd get s3://testaws1/file-aws-20 get_file-20 Wed Sep 4 11:25:42 EDT 2024 download: 's3://testaws1/file-aws-20' -> 'get_file-20' [1 of 1] ERROR: Download of 'get_file-20' failed (Reason: 403 (InvalidObjectState): Read through is not enabled for this config) Object download fails with error "ERROR: Download of './file-2' failed (Reason: 403 (InvalidObjectState): Read through is not enabled for this config)" Actual results: Object download fails with error "ERROR: Download of './file-2' failed (Reason: 403 (InvalidObjectState): Read through is not enabled for this config)" After enabling the "allow_read_through" in the zonegroup as well the object download fails. Expected results: 1. Object download should fail if restored via the was s3api restore-object and should not be dependent on the allow_read_through" parameter Additional info:
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 (Red Hat Ceph Storage 8.0 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/RHBA-2024:10216