[NEXUS-18675] log blob deleted reason for s3 based deleted blobs - Sonatype JIRA

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Critical
Resolution: Fixed
Affects Version/s: 3.13.0, 3.14.0
Fix Version/s: 3.17.0
Component/s: Logging, S3
Labels:
- supportant
- t-morpheus

Story Points:
1
Epic Link:
S3 Blob Store 2

Description

Note the file-based blobstore explicitly logs the deleted reason when it unexpectedly encounters a soft-deleted blob:

https://github.com/sonatype/nexus-public/blob/release-3.14.0-04/components/nexus-blobstore-file/src/main/java/org/sonatype/nexus/blobstore/file/FileBlobStore.java#L437

Whereas the S3 blobstore logs the S3BlobAttributes:

https://github.com/sonatype/nexus-public/blob/release-3.14.0-04/plugins/nexus-blobstore-s3/src/main/java/org/sonatype/nexus/blobstore/s3/internal/S3BlobStore.java#L321

Unfortunately that delegates to S3PropertiesFile.toString() which just dumps the bucket and key, not the actual attributes.

Acceptance

The path or bucket-key pair and the attributes for an accessed soft-deleted blob shall be logged in the warning msg.

Attachments

Issue Links

causes

NEXUS-32028 Admin - Compact blob store task logs a WARN message for every soft-deleted asset it will hard delete

New

discovered while testing

NEXUS-18648 npm requests to proxy repositories using S3BlobStorage may start permanently failing with 500

Closed

Activity

People

Assignee:: Joshua Hill

Reporter:: Peter Lynch

Last Updated By:: Peter Lynch

Team:: NXRM - Morpheus

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 12/10/18 05:20 PM

Updated:: 05/04/22 11:45 AM

Resolved:: 04/04/19 08:22 PM

Date of First Response:: 04/Apr/19 8:22 PM

tigCommentSecurity.panel-title