Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Automatically Closed
-
Affects Version/s: 3.28.0
-
Fix Version/s: 3.29.1
-
Component/s: Blobstore, Docker, Scheduled Tasks
-
Labels:
-
Epic Link:
-
Notability:2
Description
Issue:
Customer moved a docker hosted repository to a new blobstore (S3 to S3), after that docker pulls were failing "unknown blob". There were no errors in the repository-move task log.
The nexus log shows the following log entry:
2020-10-08 10:14:00,355+0000 WARN [qtp42171953-201] userA org.sonatype.nexus.blobstore.s3.internal.S3BlobStore - Attempt to access non-existent blob 23b1065b-0534-46ae-95f7-9167f1dce928 (s3://<New-S3-Blob>/content/vol-35/chap-10/23b1065b-0534-46ae-95f7-9167f1dce928.properties {})
The following did not exist in the the new S3 blobstore, but did exist in old S3 blobstore.
/content/vol-35/chap-10/23b1065b-0534-46ae-95f7-9167f1dce928.properties
Therefore not all blob files for this hosted repository was moved.
There was no reference to 23b1065b-0534-46ae-95f7-9167f1dce928 in the repository-move task log.
Expected
All blob files for a repository should be move to the new blobstore by the repository move task.
Recovery
Running the repository move task to move the repository back to the original blobstore resolved the issue.