Bug 1624320

My understanding is that oc cluster up is broken for 3.11 and the fix has been aligned to 3.11.z.

There is an issue with certificates which is impacting:
 WebUI
 Service Catalog <-> Brokers

I'm aligning this BZ to 3.11.z to match bug 1607913.  
I think once 1607913 is addressed this issue will be resolved.

https://github.com/openshift/origin/pull/20868 should fix this.

Relate code was merged in v3.11.0-0.29.0 in downstream. The latest puddle of downstream is v3.11.0-0.28.0
Waiting image ready for test.

Double checked with latest oc, test Failed although https://github.com/openshift/origin/pull/20868 was merged in v3.11.0-0.29.0 and later, the original issue still exist.

$ oc version
oc v3.11.0-0.32.0
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://127.0.0.1:8443
kubernetes v1.11.0+d4cacc0


Command:
$ oc cluster up --enable='*,service-catalog,template-service-broker' --image='brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ose-${component}:${version}'

These two images are the most likely to be out of date since the images are hard coded, so you may want to manually repull them to ensure they're up to date. The rest as far as I know respect $version so should pull images for the corresponding tag.

The service-serving-cert-signer image is hard coded to openshift/origin-service-serving-cert-signer:v3.11 so it's probably pulling from docker.io. I filed an issue regarding the version at https://github.com/openshift/origin/issues/20888, but it may be worth opening a BZ since it's affecting the downstream client too.

Our image is also hard coded to docker.io/ansibleplaybookbundle/origin-ansible-service-broker:latest. We have a BZ around this, https://bugzilla.redhat.com/show_bug.cgi?id=1612876. We're thinking the best course is working on getting our image added to the upstream openshift org so we can use and respect the --image flag setting. For now that's not possible and won't be fixed in time for 3.11.

The cluster is coming up fine. Look in the broker logs. It looks like there is a networking or name resolution issue in your environment.

oc exec -it -n openshift-automation-service-broker   openshift-automation-service-broker-1-r5zbr -c broker /bin/bash
bash-4.2$ ping hub.docker.com
ping: hub.docker.com: Name or service not known

time="2018-09-11T13:08:36Z" level=error msg="unable to generate docker hub token - Post https://hub.docker.com/v2/users/login/: dial tcp: lookup hub.docker.com on 172.30.0.2:53: read udp 172.17.0.8:39359->172.30.0.2:53: read: no route to host"
time="2018-09-11T13:08:36Z" level=error msg="unable to retrieve image names for registry dh - Post https://hub.docker.com/v2/users/login/: dial tcp: lookup hub.docker.com on 172.30.0.2:53: read udp 172.17.0.8:39359->172.30.0.2:53: read: no route to host"
time="2018-09-11T13:08:36Z" level=warning msg="registry: 0x165b980 was unable to complete bootstrap - Post https://hub.docker.com/v2/users/login/: dial tcp: lookup hub.docker.com on 172.30.0.2:53: read udp 172.17.0.8:39359->172.30.0.2:53: read: no route to host"

Jason, 

Thanks for you support.

Moving to VERIFIED since setup a cluster succeed while enalbe service-catalog and automation-service-broker by oc cluster up.

oc v3.11.0-0.32.0

Closing bugs that were verified and targeted for GA but for some reason were not picked up by errata. This bug fix should be present in current 3.11 release content.