此内容没有您所选择的语言版本。

Chapter 6. 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
Copy to Clipboard Toggle word wrap

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
Copy to Clipboard Toggle word wrap
Note

This issue may be persistent on your hardware. In this case, the only known workaround is to use a more powerful host machine.

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.

6.2. xPaaS addon causes start failure

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'.
Copy to Clipboard Toggle word wrap

To work around this issue, re-apply the addon:

$ minishift addons apply xpaas
Copy to Clipboard Toggle word wrap
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat