Red Hat Bugzilla – Bug 1622830
oc adm registry is using registry.access.redhat.com to pull image by default
Last modified: 2018-10-11 03:26:27 EDT
Description of problem: oc adm registry is using registry.access.redhat.com to pull image, it should use registry.redhat.io by default: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 13s default-scheduler Successfully assigned wzheng1/docker-registry-1-r9tz7 to qe-wzheng-311-node-1 Normal Pulling 12s kubelet, qe-wzheng-311-node-1 pulling image "registry.access.redhat.com/openshift3/ose-docker-registry:v3.11.0-0.24.0" Warning Failed 11s kubelet, qe-wzheng-311-node-1 Failed to pull image "registry.access.redhat.com/openshift3/ose-docker-registry:v3.11.0-0.24.0": rpc error: code = Unknown desc = Error reading manifest v3.11.0-0.24.0 in registry.access.redhat.com/openshift3/ose-docker-registry: error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\"" Warning Failed 11s kubelet, qe-wzheng-311-node-1 Error: ErrImagePull Normal SandboxChanged 10s kubelet, qe-wzheng-311-node-1 Pod sandbox changed, it will be killed and re-created. Normal BackOff 7s (x2 over 8s) kubelet, qe-wzheng-311-node-1 Back-off pulling image "registry.access.redhat.com/openshift3/ose-docker-registry:v3.11.0-0.24.0" Warning Failed 7s (x2 over 8s) kubelet, qe-wzheng-311-node-1 Error: ImagePullBackOff Version-Release number of selected component (if applicable): v3.11.0-0.24.0 How reproducible: always Steps to Reproduce: 1.oc adm regsitry 2. 3. Actual results: oc adm registry is using registry.access.redhat.com to pull image Expected results: it should use registry.redhat.io by default Additional info: The help page of oc adm registry needs to be updated too: Options: --images='registry.access.redhat.com/openshift3/ose-${component}:${version}': The image to base this registry on - ${component} will be replaced with --type
this value ultimately comes from $OS_IMAGE_PREFIX which must be getting set during the OCP build process. Sounds like it's currently set to registry.access.redhat.com and should be set to registry.redhat.io for 3.11+. Sending over to the release team.
Clayton, what is responsible for setting the "${OS_GO_PACKAGE}/pkg/cmd/util/variable.DefaultImagePrefix value in OSE builds? it is currently being set to registry.access.redhat.com which is incorrect. https://github.com/openshift/origin/blob/master/hack/lib/constants.sh#L124
https://github.com/openshift/ose/pull/1397
*** Bug 1624667 has been marked as a duplicate of this bug. ***
Verified with below version: oc v3.11.0-0.28.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 11s default-scheduler Successfully assigned test/docker-registry-1-5rwz6 to ip-172-18-13-50.ec2.internal Normal Pulling 9s kubelet, ip-172-18-13-50.ec2.internal pulling image "registry.redhat.io/openshift3/ose-docker-registry:v3.11.0-0.28.0" Warning Failed 8s kubelet, ip-172-18-13-50.ec2.internal Failed to pull image "registry.redhat.io/openshift3/ose-docker-registry:v3.11.0-0.28.0": rpc error: code = Unknown desc = Get https://registry.redhat.io/v2/openshift3/ose-docker-registry/manifests/v3.11.0-0.28.0
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652