atomic-openshift-node service fails to start in Openshift cluster deployed on AWS instances

Solution Verified - Updated -

Issue

  • atomic-openshift-node service fails to start in Openshift cluster deployed on AWS instances
  • node service fails with the below logs:
Dec 04 05:35:08 node.example.com atomic-openshift-node[44137]: W1204 05:35:08.606509   44137 sdn_controller.go:38] Could not find an allocated subnet for node: node.example.com, Waiting...
Dec 04 05:35:08 node.example.com atomic-openshift-node[44137]: F1204 05:35:08.606542   44137 node.go:309] error: SDN node startup failed: failed to get subnet for this host: node.example.com, error: timed out waiting for the condition

Environment

  • OpenShift Container Platform 3.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.