From f6fb7df808c190def26a3b1bf1b3a891bbb14e84 Mon Sep 17 00:00:00 2001 From: Oguzhan Ozmen Date: Thu, 9 Jan 2025 18:55:53 +0000 Subject: [PATCH] PendingReleaseNotes: add a note about tracker #67846 The "LastModified" info in S3 responses will be truncated to the exact second. This might cause conflicting data delivered to S3 clients during an upgrade of gateways. Adding this release note to raise awareness. Signed-off-by: Oguzhan Ozmen --- PendingReleaseNotes | 3 +++ 1 file changed, 3 insertions(+) diff --git a/PendingReleaseNotes b/PendingReleaseNotes index b4824a6558467..f5e3f597eea02 100644 --- a/PendingReleaseNotes +++ b/PendingReleaseNotes @@ -10,6 +10,9 @@ * use of tenant names instead of accounts in IAM policy documents, * interpretation of IAM policy without cross-account policy evaluation, * S3 API support for cross-tenant names such as `Bucket='tenant:bucketname'` +* RGW: For compatibility with AWS S3, LastModified timestamps are now truncated + to the second. Note that during upgrade, users may observe these timestamps + moving backwards as a result. * RBD: All Python APIs that produce timestamps now return "aware" `datetime` objects instead of "naive" ones (i.e. those including time zone information -- 2.39.5