Bug 2053218 - ImagePull fails with error "unable to pull manifest from example.com/busy.box:v5 invalid reference format"
Summary: ImagePull fails with error "unable to pull manifest from example.com/busy.bo...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
Depends On: 2049234
Blocks: 2053222
TreeView+ depends on / blocked
Reported: 2022-02-10 17:13 UTC by OpenShift BugZilla Robot
Modified: 2022-03-12 04:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-12 04:42:06 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift image-registry pull 308 0 None Merged Bug 2053218: Fix pull-through for images that have dots in their namespace 2022-02-14 10:04:10 UTC
Github openshift library-go pull 1310 0 None Merged [release-4.10] Bug 2053218: Fix handling namespaces with dots in registry client 2022-02-11 16:41:24 UTC
Github openshift oc pull 1067 0 None Merged Bug 2053218: Fix mirroring images that have dots in their namespace 2022-02-12 13:18:55 UTC
Github openshift openshift-apiserver pull 281 0 None Merged Bug 2053218: Fix importing images that have dots in their namespace 2022-02-21 19:48:19 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:42:24 UTC

Comment 1 XiuJuan Wang 2022-02-12 06:45:57 UTC
Verified on pr premerged.
oc version
Client Version: v4.2.0-alpha.0-1359-g50ff55b
Server Version: 4.10.0-0.ci.test-2022-02-12-053124-ci-ln-gxt32yk-latest
Kubernetes Version: v1.22.1-4775+2e8bad73c837e8-dirty

$oc image mirror uay.io/rh-test.me/busybox:latest $registry/test.myimage.a.b.c:latest --keep-manifest-list=true --filter-by-os='.*' --insecure

      quay.io/rh-test.me/busybox sha256:ec3f0931a6e6b6855d76b2d7b0be30e81860baccd891b2e243280bf1cd8ad710 1.422KiB
      quay.io/rh-test.me/busybox sha256:009932687766e1520a47aa9de3bfe97ffdb1b6cad0b08d5078bad60329f13f19 754.7KiB
      sha256:b69959407d21e8a062e0416bf13405bb2b71ed7a84dde4158ebafacfa06f5578 -> latest
  stats: shared=0 unique=2 size=756.1KiB ratio=1.00

phase 0:
  registry-wxj.apps.ci-ln-gxt32yk-72292.origin-ci-int-gce.dev.rhcloud.com test.myimage.a.b.c blobs=2 mounts=0 manifests=1 shared=0

info: Planning completed in 4.92s
uploading: registry-wxj.apps.ci-ln-gxt32yk-72292.origin-ci-int-gce.dev.rhcloud.com/test.myimage.a.b.c.d sha256:009932687766e1520a47aa9de3bfe97ffdb1b6cad0b08d5078bad60329f13f19 754.7KiB
sha256:b69959407d21e8a062e0416bf13405bb2b71ed7a84dde4158ebafacfa06f5578 registry-wxj.apps.ci-ln-gxt32yk-72292.origin-ci-int-gce.dev.rhcloud.com/test.myimage.a.b.c:latest
info: Mirroring completed in 5.12s (151.1kB/s)

$ oc import-image myimage:latest --from=$registry/test.myimage.a.b.c:latest --reference-policy=local  --insecure --confirm

$ oc run mypod --restart=Never --image=myimage:latest --image-pull-policy=Always -- echo "Hello"
pod/mypod created

  Normal  Pulling         6s    kubelet            Pulling image "image-registry.openshift-image-registry.svc:5000/wxj/myimage@sha256:0415f56ccc05526f2af5a7ae8654baec97d4a614f24736e8eef41a4591f08019"
  Normal  Pulled          6s    kubelet            Successfully pulled image "image-registry.openshift-image-registry.svc:5000/wxj/myimage@sha256:0415f56ccc05526f2af5a7ae8654baec97d4a614f24736e8eef41a4591f08019" in 164.559426ms

 $oc -n openshift-image-registry get pods -l docker-registry=default -o name | while read -r pod; do oc -n openshift-image-registry logs "$pod"; done | grep "test.myimage.a.b.c"
time="2022-02-12T06:34:42.531166997Z" level=info msg="Trying to stat \"sha256:b97242f89c8a29d13aea12843a08441a4bbfc33528f55b60366c1d8f6923d0d4\" from \"registry-wxj.apps.ci-ln-gxt32yk-72292.origin-ci-int-gce.dev.rhcloud.com/test.myimage.a.b.c\" with a fall-back to insecure transport" go.version=go1.17.5 http.request.host="image-registry.openshift-image-registry.svc:5000" http.request.id=317d22ca-467b-4a56-8b86-8eea6f67d574 http.request.method=GET http.request.remoteaddr="" http.request.uri="/v2/wxj/myimage/blobs/sha256:b97242f89c8a29d13aea12843a08441a4bbfc33528f55b60366c1d8f6923d0d4" http.request.useragent="cri-o/1.23.1-3.rhaos4.10.git53ada6d.el8 go/go1.17.5 os/linux arch/amd64" openshift.auth.user="system:serviceaccount:wxj:default" vars.digest="sha256:b97242f89c8a29d13aea12843a08441a4bbfc33528f55b60366c1d8f6923d0d4" vars.name=wxj/myimage

Comment 4 XiuJuan Wang 2022-02-16 03:05:05 UTC
Those prs merged in 4.10.0-0.nightly-2022-02-15-041303

Comment 7 errata-xmlrpc 2022-03-12 04:42:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.