unable to recognize servicecatalog.k8s.io/v1beta1, Kind=ClusterServiceBroker

[david-martin]

service "asb-etcd" created
serviceaccount "asb" created
clusterrolebinding "asb" created
clusterrole "asb-auth" created
clusterrolebinding "asb-auth-bind" created
clusterrole "access-asb-role" created
persistentvolumeclaim "etcd" created
deploymentconfig "asb" created
deploymentconfig "asb-etcd" created
secret "asb-auth-secret" created
secret "registry-auth-secret" created
secret "etcd-auth-secret" created
secret "broker-etcd-auth-secret" created
configmap "broker-config" created
serviceaccount "ansibleservicebroker-client" created
clusterrolebinding "ansibleservicebroker-client" created
secret "ansibleservicebroker-client" created
route "asb-1338" created
error: unable to recognize servicecatalog.k8s.io/v1beta1, Kind=ClusterServiceBroker: no matches for servicecatalog.k8s.io/, Kind=ClusterServiceBroker
unexpected exit of OpenShift Ansible Broker (OAB) installation script

ping @philbrookes

[david-martin]

this worked the second time (the first time I enabled the addon after minishift started)

-- Applying addon 'minishift-mobilecore-addon':..................
Installing and starting MCP extension, this can take a while
....
Installing Ansible Service Broker with Container Repository Organisation: aerogearcatalog
..
mobile core successfully enabled

I'll close this and put it down to timing the first time. If it happens again I'll try add more info

[psturc]

Hit the issue just now...

 minishift start --openshift-version v3.9.0 --service-catalog
Addon 'minishift-mobilecore-addon' installed
Add-on 'minishift-mobilecore-addon' enabled
No Minishift instance exists. New 'cpus' setting will be applied on next 'minishift start'
No Minishift instance exists. New 'memory' setting will be applied on next 'minishift start'
-- Starting profile 'minishift'
-- Checking if requested OpenShift version 'v3.9.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.9.0' is supported ... OK
-- Checking if requested hypervisor 'xhyve' is supported on this platform ... OK
-- Checking if xhyve driver is installed ...
   Driver is available at /usr/local/bin/docker-machine-driver-xhyve
   Checking for setuid bit ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting local OpenShift cluster using 'xhyve' hypervisor ...
-- Minishift VM will be configured with ...
   Memory:    4 GB
   vCPUs :    2
   Disk size: 20 GB
-- Starting Minishift VM ..................... OK
-- Checking for IP address ... OK
-- Checking for nameservers ... OK
-- Checking if external host is reachable from the Minishift VM ...
   Pinging 8.8.8.8 ... FAIL
   VM is unable to ping external host
-- Checking HTTP connectivity from the VM ...
   Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 0% used OK
   Importing 'openshift/origin:v3.9.0' . CACHE MISS
   Importing 'openshift/origin-docker-registry:v3.9.0' . CACHE MISS
   Importing 'openshift/origin-haproxy-router:v3.9.0' . CACHE MISS
-- OpenShift cluster will be configured with ...
   Version: v3.9.0
Pulling image openshift/origin:v3.9.0
Pulled 1/4 layers, 26% complete
Pulled 2/4 layers, 68% complete
Pulled 3/4 layers, 90% complete
Pulled 4/4 layers, 100% complete
Extracting
Image pull complete
Using Docker shared volumes for OpenShift volumes
Using 192.168.64.8 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
OpenShift server started.

The server is accessible via web console at:
    https://192.168.64.8:8443

You are logged in as:
    User:     developer
    Password: <any value>

To login as administrator:
    oc login -u system:admin

-- Applying addon 'minishift-mobilecore-addon':..................
Installing and starting MCP extension, this can take a while
....
Installing Ansible Service Broker with Container Repository Organisation: aerogearcatalog
.Error during post cluster up configuration: Error executing command 'ssh command error:
command : bash ~/mobile-core/installer/roles/ansible-service-broker-setup/files/provision-ansible-service-broker.sh '<hidden-dockerid>' '<hidden-dockerpass>' 'aerogearcatalog' true latest 192.168.64.8 nip.io ansible-service-broker
err     : exit status 1
output  : starting install of OpenShift Ansible Broker (OAB)
Logged into "https://127.0.0.1:8443" as "system:admin" using existing credentials.

You have access to the following projects and can switch between them with 'oc project <projectname>':

  * default
    kube-public
    kube-service-catalog
    kube-system
    myproject
    openshift
    openshift-infra
    openshift-node
    openshift-template-service-broker
    openshift-web-console

Using project "default".
Now using project "ansible-service-broker" on server "https://127.0.0.1:8443".

You can add applications to this project with the 'new-app' command. For example, try:

    oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git

to build a new example application in Ruby.
Generating a 4096 bit RSA private key
......++
.....................................................................................................++
writing new private key to '/tmp/etcd-cert/key.pem'
-----
Generating RSA private key, 2048 bit long modulus
.......................+++
...................................................................+++
e is 65537 (0x10001)
Signature ok
subject=/CN=client
Getting CA Private Key
error: unable to process template: Post https://127.0.0.1:8443/apis/template.openshift.io/v1/namespaces/ansible-service-broker/processedtemplates: dial tcp 127.0.0.1:8443: getsockopt: connection refused
error: no objects passed to create
unexpected exit of OpenShift Ansible Broker (OAB) installation script
':

Update: Sorry, this a bit different error, but I got the same as the one above when I was trying to run the minishift for the first time. There was also an error with Installing Ansible Service Broker with Container Repository Organisation as with this one

Update vol. 2: Using virtualbox (minishift config set vm-driver virtualbox) solved the issue for me, but the installation and using the OpenShift is significantly slower on my machine compared to using xhyve.

[psturc]

Got the same error now when using hyperkit

export CONTAINER_REPO_USERNAME=<MYUSERNAME>
export CONTAINER_REPO_PASSWORD="<MYPASS>"
export CONTAINER_REPO_ORG=aerogearcatalog
minishift addons install -f minishift-mobilecore-addon
minishift addons enable minishift-mobilecore-addon
minishift config set addon-env CONTAINER_REPO_USERNAME=${CONTAINER_REPO_USERNAME},CONTAINER_REPO_PASSWORD=${CONTAINER_REPO_PASSWORD}
minishift config set cpus 2
minishift config set memory 4096
minishift config set service-catalog true
minishift config set vm-driver hyperkit
minishift start --openshift-version v3.9.0
Addon 'minishift-mobilecore-addon' installed
Add-on 'minishift-mobilecore-addon' enabled
No Minishift instance exists. New 'cpus' setting will be applied on next 'minishift start'
No Minishift instance exists. New 'memory' setting will be applied on next 'minishift start'
No Minishift instance exists. New 'vm-driver' setting will be applied on next 'minishift start'
-- Starting profile 'minishift'
-- Checking if requested OpenShift version 'v3.9.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.9.0' is supported ... OK
-- Checking if requested hypervisor 'hyperkit' is supported on this platform ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting local OpenShift cluster using 'hyperkit' hypervisor ...
-- Minishift VM will be configured with ...
   Memory:    4 GB
   vCPUs :    2
   Disk size: 20 GB
-- Starting Minishift VM ..................... OK
-- Checking for IP address ... OK
-- Checking for nameservers ... OK
-- Checking if external host is reachable from the Minishift VM ...
   Pinging 8.8.8.8 ... FAIL
   VM is unable to ping external host
-- Checking HTTP connectivity from the VM ...
   Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 0% used OK
   Importing 'openshift/origin:v3.9.0' ................. OK
   Importing 'openshift/origin-docker-registry:v3.9.0' ... OK
   Importing 'openshift/origin-haproxy-router:v3.9.0' ..... OK
-- OpenShift cluster will be configured with ...
   Version: v3.9.0
Using Docker shared volumes for OpenShift volumes
Using 192.168.64.12 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
OpenShift server started.

The server is accessible via web console at:
    https://192.168.64.12:8443

You are logged in as:
    User:     developer
    Password: <any value>

To login as administrator:
    oc login -u system:admin

-- Applying addon 'minishift-mobilecore-addon':..................
Installing and starting MCP extension, this can take a while
....
Installing Ansible Service Broker with Container Repository Organisation: aerogearcatalog
.Error during post cluster up configuration: Error executing command 'ssh command error:
command : bash ~/mobile-core/installer/roles/ansible-service-broker-setup/files/provision-ansible-service-broker.sh '<MYUSERNAME>' '<MYPASS>' 'aerogearcatalog' true latest 192.168.64.12 nip.io ansible-service-broker
err     : exit status 1
output  : starting install of OpenShift Ansible Broker (OAB)
Logged into "https://127.0.0.1:8443" as "system:admin" using existing credentials.

You have access to the following projects and can switch between them with 'oc project <projectname>':

  * default
    kube-public
    kube-system
    myproject
    openshift
    openshift-infra
    openshift-node
    openshift-web-console

Using project "default".
Now using project "ansible-service-broker" on server "https://127.0.0.1:8443".

You can add applications to this project with the 'new-app' command. For example, try:

    oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git

to build a new example application in Ruby.
Generating a 4096 bit RSA private key
...........................................................................++
..........................................................++
writing new private key to '/tmp/etcd-cert/key.pem'
-----
Generating RSA private key, 2048 bit long modulus
.................................................+++
...............+++
e is 65537 (0x10001)
Signature ok
subject=/CN=client
Getting CA Private Key
service "asb" created
service "asb-etcd" created
serviceaccount "asb" created
clusterrolebinding "asb" created
clusterrole "asb-auth" created
clusterrolebinding "asb-auth-bind" created
clusterrole "access-asb-role" created
persistentvolumeclaim "etcd" created
deploymentconfig "asb" created
deploymentconfig "asb-etcd" created
secret "asb-auth-secret" created
secret "registry-auth-secret" created
secret "etcd-auth-secret" created
secret "broker-etcd-auth-secret" created
configmap "broker-config" created
serviceaccount "ansibleservicebroker-client" created
clusterrolebinding "ansibleservicebroker-client" created
secret "ansibleservicebroker-client" created
route "asb-1338" created
error: unable to recognize servicecatalog.k8s.io/v1beta1, Kind=ClusterServiceBroker: no matches for servicecatalog.k8s.io/, Kind=ClusterServiceBroker
unexpected exit of OpenShift Ansible Broker (OAB) installation script
':

[david-martin]

(reopening) @philbrookes Thoughts on this error? It looks like a timing issue to me where the catalog isn't running/registered when the broker is being configured

[david-martin]

Seen on Fedora 25, 27, and macos high sierra 10.13.4

[david-martin]

Seeing another variation of this error

-- Starting profile 'minishift'
-- Checking if requested OpenShift version 'v3.9.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.9.0' is supported ... OK
-- Checking if requested hypervisor 'virtualbox' is supported on this platform ... OK
-- Checking if VirtualBox is installed ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
-- Starting Minishift VM ..................... OK
-- Checking for IP address ... OK
-- Checking for nameservers ... OK
-- Checking if external host is reachable from the Minishift VM ... 
   Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ... 
   Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 17% used OK
-- OpenShift cluster will be configured with ...
   Version: v3.9.0
Deleted existing OpenShift container
Using Docker shared volumes for OpenShift volumes
Using 192.168.99.100 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
-- Starting OpenShift container ... 
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
   OpenShift server started
-- Registering template service broker with service catalog ... FAIL
   Error: cannot register the template service broker
   Caused By:
     Error: cannot create objects from template openshift-infra/template-service-broker-registration
     Caused By:
       Error: the server could not find the requested resource (post clusterservicebrokers.servicecatalog.k8s.io)

[wtrocki]

Hit that problem as well

EDIT: I can reproduce that every time I run minishift. Subsequent launches do not resolve the problem.

[david-martin]

Related minishift issue https://github.com/minishift/minishift/issues/2116 (which is linked to a few other issues too)