Writing a blob for retention can fail if the object is already locked. The transaction should be rolled back when this happens.
An error should be displayed in the ui and the retention date on the doc should not be modified.
2024-09-26T11:33:42,038 ERROR [TransactionalBlobStore] Failed to commit update of blob: 45da2a77-5b14-4b6f-9746-f44562ce8292@iFH5YV1DPKctEovdzvX7vKQqsV19KDz1 java.io.IOException: com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied because object protected by object lock. (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 8PVR928HVWK8362J; S3 Extended Request ID: cMry5jj3S4z23w7wyA+PhkNkAVGDtl63OMcpZqB72sDjmU8GagHOIbkFjC6wYY1ldoqJFmwrE3o=; Proxy: null), S3 Extended Request ID: cMry5jj3S4z23w7wyA+PhkNkAVGDtl63OMcpZqB72sDjmU8GagHOIbkFjC6wYY1ldoqJFmwrE3o= at org.nuxeo.ecm.blob.s3.S3BlobStore.writeBlobProperties(S3BlobStore.java:859) ~[nuxeo-core-binarymanager-s3-2021.61-SNAPSHOT.jar:?] at org.nuxeo.ecm.core.blob.CachingBlobStore.writeBlobProperties(CachingBlobStore.java:239) ~[nuxeo-core-api-2021.61-SNAPSHOT.jar:?]
- is related to
-
NXP-28952 Fix retention/legal hold with S3 transactional blob store
- Resolved