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 <oozmen@bloomberg.net>

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index b4824a65584676353bcd61e14be49773cb0e6581..f5e3f597eea02646d195f4bc22d1a2646035428f 100644 (file)
--- 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