OpenShift services fail to restart after configuring vSphere Cloud Provider
Issue
After configuring the vSphere Cloud Provider I can no longer restart the atomic-openshift-node service:
Mar 13 12:51:03 ocp-infra-1 atomic-openshift-node[8428]: W0313 12:51:03.492934 8428 sdn_controller.go:38] Could not find an allocated subnet for node: ocp-infra-1.example.com, Waiting...
Mar 13 12:51:03 ocp-infra-1 atomic-openshift-node[8428]: F0313 12:51:03.492972 8428 node.go:309] error: SDN node startup failed: failed to get subnet for this host: ocp-infra-1.example.com, error:
timed out waiting for the condition
Mar 13 12:51:03 ocp-infra-1 systemd[1]: atomic-openshift-node.service: main process exited, code=exited, status=255/n/a
Mar 13 12:51:03 ocp-infra-1 systemd[1]: Failed to start OpenShift Node.
Mar 13 12:51:03 ocp-infra-1 systemd[1]: Unit atomic-openshift-node.service entered failed state.
Mar 13 12:51:03 ocp-infra-1 systemd[1]: atomic-openshift-node.service failed.
Environment
- Red Hat OpenShift Container Platform 3.6 and earlier
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
