Description of problem: It is still using registry.access.redhat.com for oc cluster up help page for option --image Version-Release number of selected component (if applicable): oc v3.11.0-0.14.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: always Steps to Reproduce: 1.oc cluster up --help 2. 3. Actual results: Options: >>>>>>>>>>>>>>>>> --image='registry.access.redhat.com/openshift3/ose-${component}:${version}': Specify the images to use for OpenShift Expected results: It needs to be updated to registry.redhat.io Additional info:
And oc cluster up still uses registry.access.redhat.com to pull image by default: # oc cluster up Getting a Docker client ... Checking if image registry.access.redhat.com/openshift3/ose-control-plane:v3.11 is available ... Pulling image registry.access.redhat.com/openshift3/ose-control-plane:v3.11 error: error pulling Docker image registry.access.redhat.com/openshift3/ose-control-plane:v3.11
I was not able to trace this in origin repo, guess this must be some magic for OSE?
Clayton?
probably a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1622830#c1 (same root cause, we need the release process to change how they are setting the default image template value).
this should not be pushed out of 3.11. We need to be using the new registry correctly when 3.11 GAs, not fixing it in an errata.
Moving over to the release team
https://github.com/openshift/ose/pull/1397
Verified with below version: [root@preserve-devexp-cluster-test ~]# oc version oc v3.11.0-0.28.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO [root@preserve-devexp-cluster-test ~]# oc cluster up Getting a Docker client ... Checking if image registry.redhat.io/openshift3/ose-control-plane:v3.11 is available ... Pulling image registry.redhat.io/openshift3/ose-control-plane:v3.11 error: error pulling Docker image registry.redhat.io/openshift3/ose-control-plane:v3.11
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days