-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.12.z
-
Important
-
None
-
False
-
Description of problem:
Cannot Pull Image When using ImageStream name in DeploymentConfig as image value, the actual image in the Pod gets resolved to docker.io instead of internal registry.
Version-Release number of selected component (if applicable):
OCP 4.12
How reproducible:
Always
Steps to Reproduce:
1. Deploy an ImageStream pointing to an existing image in internal mirror registry ~~~ apiVersion: image.openshift.io/v1 kind: ImageStream metadata: name: oraclelinux namespace: default spec: lookupPolicy: local: true tags: - annotations: null from: kind: DockerImage name: <internal_mirrorresgistry>/os/oraclelinux:9 generation: 20 importPolicy: importMode: Legacy name: "9" referencePolicy: type: Source ~~~ 2. Deploy a DeploymentConfig pointing to the IS from step 1 ~~~ oc -n default create deploy oraclelinux --image=oraclelinux:9 ~~~ 3. Resulting pod fails with ImagePull error. oraclelinux:9 image pull is failing, the cluster will behave as if it is pulling these images from DockerHub (docker.io), which is not where the images are stored. . ~~~ Failed to pull image "oraclelinux:9": reading manifest latest in docker.io/library/$IMAGESTREAM_NAME: requested access to the resource is denied ~~~
Actual results:
~~~ requested access to the resource is denied ~~~
Expected results:
Pod pulls the image referenced by ImageStream from internal registry
Additional info:
Similar BUG https://bugzilla.redhat.com/show_bug.cgi?id=2000216 has been already reported and fixed in 4.10.3 errata