ansibleplaybookbundle/ansible-playbook-bundle

On and off failure during mini shift start: not yet ready to handle request

mkanoor opened this issue · 5 comments

mkanoor commented

When I run the

minishift start --vm-driver=virtualbox --service-catalog

It generates an error

-- 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: clusterservicebrokers.servicecatalog.k8s.io "template-service-broker" is forbidden: not yet ready to handle request
Error during 'cluster up' execution: Error starting the cluster.

Is this a timing issue?

This is the whole sequence of output

 -- Starting profile 'minishift'
-- Checking if requested OpenShift version 'v3.7.1' is valid ... OK
-- Checking if requested OpenShift version 'v3.7.1' 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 ...
-- Minishift VM will be configured with ...
   Memory:    2 GB
   vCPUs :    2
   Disk size: 20 GB
-- Starting Minishift VM ............................ OK
-- Checking for IP address ... 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 ... 1% used OK
   Importing 'openshift/origin:v3.7.1' ........... OK
   Importing 'openshift/origin-docker-registry:v3.7.1' .. OK
   Importing 'openshift/origin-haproxy-router:v3.7.1' .. OK
-- OpenShift cluster will be configured with ...
   Version: v3.7.1
Starting OpenShift using openshift/origin:v3.7.1 ...
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:v3.7.1 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ... 
   Using nsenter mounter for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ... 
   Using 192.168.99.101 as the server IP
-- Checking service catalog version requirements ... OK
-- Starting OpenShift container ... 
   Creating initial OpenShift configuration
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
   OpenShift server started
-- Adding default OAuthClient redirect URIs ... OK
-- Installing registry ... 
   scc "privileged" added to: ["system:serviceaccount:default:registry"]
-- Installing router ... OK
-- Importing image streams ... OK
-- Importing templates ... OK
-- Importing service catalog templates ... OK
-- Installing service catalog ... OK
-- Installing template service broker ... OK
-- 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: clusterservicebrokers.servicecatalog.k8s.io "template-service-broker" is forbidden: not yet ready to handle request
Error during 'cluster up' execution: Error starting the cluster.
eriknelson commented
djzager commented

@mkanoor your contribution is appreciated. I'm not sure though that an issue against this project is the most prudent route. Have you discussed this issue with any one from the minishift project. This looks (albeit at a glance) like an issue with the service-catalog component of minishift.

mkanoor commented

@eriknelson @djzager
Is it possible to figure out from the logs what failed during the
Registering template service broker with service catalog ... FAIL because I think the install went fine
-- Installing template service broker ... OK

djzager commented

@mkanoor
It's worth pointing out that this project in particular has no ties to minishift, service catalog, or the template service broker. That is the reason @eriknelson and myself were pointing you to the minishift project.

Your initial guess appears a reasonable one...that this is a timing issue. I don't know the specifics of how minishift brings up the service catalog + template service broker. That is why talking with the people working on the minishift project is your best route for finding a resolution to your problem.

Edit: missing a word 😎