-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.13.z, 4.12.z
-
No
-
False
-
Description of problem:
While using "rhel-minimal" shortname in 4.11, the crio is trying to pull correct image that is "registry.access.redhat.com/rhel-minimal:latest" 45m Normal Pulled pod/mysql-1-l42wt Successfully pulled image "registry.access.redhat.com/rhel-minimal:latest" in 584.0265ms But from 4.12, if we use "rhel-minimal", crio is trying to pull an image which is not existing ie, "registry.access.redhat.com/rhel-minimum" 13m Warning Failed pod/test-412-rhel-7fdbc68586-lvj5z Failed to pull image "rhel-minimal": rpc error: code = Unknown desc = reading manifest latest in registry.access.redhat.com/rhel-minimum: name unknown: Repo not found It seems the redirection to "registry.access.redhat.com" is happening successfully in 4.12 cluster as well but the mapping of image against rhel-minimal has some issues.Any pointers on this would be helpful
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a deployment with short image name "rhel-minimal" in 4.12 cluster
Actual results:
Getting "imagepullerror" and also the error message showing "rhel-minimum"(registry.access.redhat.com/rhel-minimum) when the image provided in deployment yaml is "rhel-minimal" "Failed to pull image "rhel-minimal": rpc error: code = Unknown desc = reading manifest latest in registry.access.redhat.com/rhel-minimum: name unknown: Repo not found"
Expected results:
Try to pull "rhel-minimal" image instead of "rhel-minimum"
Additional info:
Shortname for "rhel-minimal" mapped wrongly here to "rhel-minimum" https://github.com/containers/shortnames/blob/main/shortnames.conf#L59
- links to