-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 10.10-HF34
-
Fix Version/s: 10.10-HF36, 11.4, 2021.0
On regular S3 buckets, we get this exception in the logs at startup:
2020-10-29T15:00:01,122 WARN [S3BlobStoreConfiguration] Failed to get ObjectLockConfiguration for bucket: mybucket com.amazonaws.services.s3.model.AmazonS3Exception: Object Lock configuration does not exist for this bucket (Service: Amazon S3; Status Code: 404; Error Code: ObjectLockConfigurationNotFoundError; Request ID: AH4S2S2MFK1Q2V8P; S3 Extended Request ID: RyrfrlZMJpG6gLOdFGiVzWjMKlX7VH/rnqQORCKJ7Xi5Y+COh3I13S6zUWMdc+qNG4lWyiVPR/4=; Proxy: null) at org.nuxeo.ecm.blob.s3.S3BlobStoreConfiguration.computeBucketRetentionMode(S3BlobStoreConfiguration.java:441) ~[nuxeo-core-binarymanager-s3-10.10-HF34.jar:?] at org.nuxeo.ecm.blob.s3.S3BlobStoreConfiguration.<init>(S3BlobStoreConfiguration.java:222) ~[nuxeo-core-binarymanager-s3-10.10-HF34.jar:?] at org.nuxeo.ecm.blob.s3.S3BlobProvider.getConfiguration(S3BlobProvider.java:108) ~[nuxeo-core-binarymanager-s3-10.10-HF34.jar:?] at org.nuxeo.ecm.blob.s3.S3BlobProvider.getBlobStore(S3BlobProvider.java:76) ~[nuxeo-core-binarymanager-s3-10.10-HF34.jar:?] at org.nuxeo.ecm.core.blob.BlobStoreBlobProvider.initialize(BlobStoreBlobProvider.java:60) ~[nuxeo-core-api-10.10-HF34.jar:?]
This message is harmless but should actually be hidden, as it's normal for a regular bucket to not have object lock configuration.
- depends on
-
NXP-29476 Include Content-MD5 HTTP header for S3 Object Lock
- Resolved
- Is referenced in
(2 Is referenced in)