Many thanks for your help Jeff. Based on your input, I have updated my installation script and service catalog is correctly installed. Apparently there was a mistmatch between oc client installed locally and version oc the cluster to be created
https://github.com/snowdrop/cloud-native-infra/blob/master/oc/install_ocp.sh On Wed, Mar 21, 2018 at 3:33 PM, Jeff Peeler <[email protected]> wrote: > > On Tue, Mar 20, 2018 at 1:46 PM, Charles Moulliard <[email protected]> > wrote: > >> Hi, >> >> When oc cluster up start with param "--service-catalog=true" then it will >> fail and this error about template not found is reported >> >> [root@cloud ~]# systemctl status openshift.service >> ● openshift.service - OpenShift oc cluster up Service >> Loaded: loaded (/etc/systemd/system/openshift.service; enabled; >> vendor preset: disabled) >> Active: failed (Result: exit-code) since Tue 2018-03-20 17:42:05 UTC; >> 33s ago >> Process: 3819 ExecStart=/usr/local/bin/oc cluster up >> --host-config-dir=/var/lib/openshift/config >> --host-data-dir=/var/lib/openshift/data --host-pv-dir=/tmp >> --host-volumes-dir=/var/lib/openshift/volumes --use-existing-config=true >> --public-hostname=192.168.99.50 --routing-suffix=192.168.99.50.nip.io >> --loglevel=1 --service-catalog=true (code=exited, status=1/FAILURE) >> Main PID: 3819 (code=exited, status=1/FAILURE) >> >> Mar 20 17:42:05 cloud occlusterup[3819]: FAIL >> Mar 20 17:42:05 cloud occlusterup[3819]: Error: cannot register the >> template service broker >> Mar 20 17:42:05 cloud occlusterup[3819]: Caused By: >> *Mar 20 17:42:05 cloud occlusterup[3819]: Error: cannot retrieve template >> "template-service-broker-registration" from namespace "openshift-infra"* >> Mar 20 17:42:05 cloud occlusterup[3819]: Caused By: >> Mar 20 17:42:05 cloud occlusterup[3819]: Error: >> templates.template.openshift.io "template-service-broker-registration" >> not found >> Mar 20 17:42:05 cloud systemd[1]: openshift.service: main process exited, >> code=exited, status=1/FAILURE >> Mar 20 17:42:05 cloud systemd[1]: Failed to start OpenShift oc cluster up >> Service. >> Mar 20 17:42:05 cloud systemd[1]: Unit openshift.service entered failed >> state. >> Mar 20 17:42:05 cloud systemd[1]: openshift.service failed. >> >> >> Is there a workaround ? >> > > What version is that oc binary you're using? I ask to ensure that it's in > sync with what release you're trying to deploy. > > It looks like there have been several related reports while using > minishift (I assume minishift uses a systemd service for launching oc > cluster up): > https://github.com/minishift/minishift/issues/2116 > https://github.com/minishift/minishift/issues/1908 > https://github.com/minishift/minishift/issues/1910 > > This report outlines that using existing config is the problem: > https://github.com/openshift/origin/issues/18119 > > I've tried reproducing failure on 3.7.0, 3.7.1, and 3.7.2 with cluster up > and all have worked for me, but this is without minishift or existing > config in the mix. The exact command used was "oc cluster up > --version=v3.7.2 --service-catalog". > > Hope that's somewhat helpful. >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
