-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Package Repositories
-
Tags:
-
Sprint:DevTools-13
After nexus HA deployment, we sometimes get errors between nexus local metadatas and the S3 blobstore metadatas.
2020-01-02 09:08:03,049+0000 WARN [qtp1973610446-16890] pod-0 deployment org.sonatype.nexus.repository.docker.internal.V2Handlers - Is the remote url a valid docker endpoint? Remote host https://artifactory.arondor.cloud:5001/ with path /v2/arender-hmi/manifests/4.0.6.NX1.0 did not return the expected response. Error message: The named manifest is not known to the registry.
A way to address this is to delete the culprit blob/metadata directly in the nexus UI followed by running the reconcile blobstore metadatas task.
But It seems it only fix the issue in the nexus node we are logged in to and not on every nodes in the cluster.