We are experiencing a sudden issue with the Nexus OSS caché for an internal repository.
Sometimes, when a new version of a certain internal component is uploaded to Nexus (using the /service api), it marks the current version to be deleted (soft-delete), but the new one is not being updated in the cache, so this causes this component to be unavailable.
2024-07-12 17:20:15,040+0000 WARN [qtp1484064123-274292] *UNKNOWN org.sonatype.nexus.blobstore.s3.internal.S3BlobStore - Attempt to access soft-deleted blob eacac4e0-f38c-42d4-a30b-232e71f26xxx attributes: s3://xx-artifacts-npm/internal/content/vol-22/chap-21/eacac4e0-f38c-42d4-a30b-232e71f26xxx.properties {deletedDateTime=1720804814825, deleted=true, @BlobStore.created-by=npm-deployer, creationTime=1720798547335, @BlobStore.created-by-ip=10.52.67.XXX, @BlobStore.content-type=application/json, sha1=0386afcad0d26130d5d7d990ced050edcab79xxx, @BlobStore.blob-name=@andes/listbox, deletedReason=Updating asset AttachedEntityId{asset->#63:62972}, @Bucket.repo-name=internal, size=2834400}
2024-07-12 17:20:15,044+0000 WARN [qtp1484064123-123456] *UNKNOWN com.sonatype.nexus.repository.npm.internal.orient.NpmStreamPayload - Missing blob for asset Asset{metadata=AttachedEntityMetadata{schema=asset, document=#63:62972{bucket:#48:0,format:npm,last_updated:Fri Jul 12 16:52:49 GMT 2024,attributes:[5],component:null,name:@andes/listbox,size:2834400,content_type:application/json,created_by:npm-deployer,created_by_ip:10.52.67.188,blob_ref:internal-s3@eacac4e0-f38c-42d4-a30b-232e71f26xxx,last_downloaded:Fri Jul 12 16:52:49 GMT 2024,blob_created:Wed Jan 04 17:12:40 GMT 2023,blob_updated:Fri Jul 12 15:35:47 GMT 2024} v1598}, name=@andes/listbox} and no handler set to recover, for package '@andes/listbox' and rev 'unknown'
To make things weirder, the internal repository deployment policy is set as “disable redeploy” so, not sure why this is marking an existing component to be deleted.
Nexus OSS Version : 3.49.0-02
Operative System : Ubuntu 20.04.4 LTS
Database : OrientDB (Embed DB)