Chapter 7. OpenShift Container Platform cluster times out waiting for response from API server
When starting the cluster via minishift start
, you may encounter the following error message:
Error: timed out waiting for the condition
Error: timed out waiting for the condition
Cause: This issue is caused by oc cluster up
, which is used by Container Development Kit to start the OpenShift Container Platform cluster. The underlying cause of the timeout is unknown.
Workaround: Delete the existing Container Development Kit virtual machine, then retry starting the cluster using the following commands:
minishift delete minishift start
$ minishift delete
$ minishift start
This issue may be persistent on your hardware. In this case, the only known workaround is to use a more powerful host machine.
7.1. Building FUSE templates with registry.redhat.io streams fails Copy linkLink copied to clipboard!
When you attempt to build a FUSE template, it fails because the template specifies that images are to be pulled from registry.redhat.io, and credentials for the registry are not included in the myproject OpenShift namespace used by Container Development Kit. This works as expected in the openshift namespace.
7.2. xPaaS addon causes start failure Copy linkLink copied to clipboard!
When running minishift start
and the xPaaS addon is applied before the API server becomes responsive, the process fails with the following error message:
Error during post cluster up configuration: Error executing command 'oc apply -f v#{OPENSHIFT_VERSION}/xpaas-streams -n openshift'.
Error during post cluster up configuration: Error executing command 'oc apply -f v#{OPENSHIFT_VERSION}/xpaas-streams -n openshift'.
To work around this issue, re-apply the addon:
minishift addons apply xpaas
$ minishift addons apply xpaas