Description of problem: Setup OCP on OpenStack with cloud provider enabled, node service could not be successfully started. Ansible installer failed at task 'openshift_node : Start and enable node'. Version-Release number of selected component (if applicable): atomic-openshift-node-3.5.0.16-1.git.0.a26133a.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Setup OCP on OpenStack with cloud provider enabled. Actual results: Ansible installer failed running task 'openshift_node : Start and enable node'. Dug into log I found: ``` Feb 4 05:13:01 host-8-174-100 atomic-openshift-node: W0204 05:13:01.962769 22753 controller.go:71] Could not find an allocated subnet for node: qe-jhou-master-1, Waiting... Feb 4 05:13:01 host-8-174-100 atomic-openshift-node: F0204 05:13:01.962790 22753 node.go:351] error: SDN node startup failed: Failed to get subnet for this host: qe-jhou-master-1, error: timed out waiting for the condition ``` Then in /etc/origin/node/node-config.yaml the nodeName was set as 'nodeName: qe-jhou-master-1', it needs to be overwritten by actual hostname 'host-8-174-100.host.centralci.eng.rdu2.redhat.com'. After changing nodeName in the node config, node service was started successfully. Expected results: Installer should properly set node-config.yaml before starting node service. Additional info:
This bug is should be a dup with BZ#1416703, they have the same root cause.
*** This bug has been marked as a duplicate of bug 1416703 ***