Description of problem:

When attempting to restore or download objects that have been cloud transitioned, the system throws a "403 (InvalidObjectState): Read through is not enabled for this config" error. 

This occurs because the "read-through" option was not enabled during the object's transition. 

This enhancement request aims to allow the restoration of such objects via the read-through mechanism after the "read-through" option has been enabled, even if it was not originally configured during the object transition.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Transition an object to a cloud storage without enabling the "read-through" option.

2. Attempt to download or access the object via a read request.
Observe the error: ERROR: S3 error: 403 (InvalidObjectState): Read through is not enabled for this config.

(venv) [root@ceph-pri-tfa-vim-toraoc-node4 rgw]# date; s3cmd get s3://testcloud-1/file-3 file-3-aws-testcloud-1
Wed Sep  4 04:24:04 EDT 2024
download: 's3://testcloud-1/file-3' -> 'file-3-aws-testcloud-1'  [1 of 1]
ERROR: Download of 'file-3-aws-testcloud-1' failed (Reason: 403 (InvalidObjectState): Read through is not enabled for this config)
ERROR: S3 error: 403 (InvalidObjectState): Read through is not enabled for this config
 
3. Enable the "read-through" option in the zonegroup configuration.

4. Attempt to download or access the previously cloud-transitioned again.

Actual results:

The error persists, preventing the restoration of the object via read-through.
Expected results:


Impact: 

- This enhancement will provide backward compatibility for cloud-transitioned objects in older versions or before the available read-through option.

- The change aligns with the expectation that enabling read-through should apply to all objects, not just those transitioned after the setting was enabled.