Actions
Bug #68010
closedrgw/cloud-restore: For temporary restored objects, if the `restore-object` request is retried, update expiry_date
% Done:
0%
Source:
Backport:
tentacle
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
backport_processed
Merge Commit:
Fixed In:
v20.3.0-2400-gdd3662825d
Released In:
Upkeep Timestamp:
2025-08-16T17:50:35+00:00
Tags:
Description
This is related to cloud-restore feature (https://tracker.ceph.com/issues/67679). As per AWS spec (https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html),
After restoring an archived object, you can update the restoration period by reissuing the request with a new period. Amazon S3 updates the restoration period relative to the current time and charges only for the request-there are no data transfer charges. You cannot update the restoration period when Amazon S3 is actively processing your current restore request for the object.
<<<
This still needs to be handled.
Updated by Soumya Koduri 9 months ago
- Status changed from New to Fix Under Review
- Pull request ID set to 64804
Updated by Upkeep Bot 9 months ago
- Status changed from Fix Under Review to Resolved
- Merge Commit set to dd3662825d940914f70c9e43aeed2ad96b0a386a
- Fixed In set to v20.3.0-2400-gdd3662825d
- Upkeep Timestamp set to 2025-08-16T17:50:35+00:00
Updated by Soumya Koduri 7 months ago
- Status changed from Resolved to Pending Backport
- Backport set to tentacle
Updated by Upkeep Bot 7 months ago
- Copied to Backport #73408: tentacle: rgw/cloud-restore: For temporary restored objects, if the `restore-object` request is retried, update expiry_date added
Updated by J. Eric Ivancich 6 months ago
- Status changed from Pending Backport to Resolved
Actions