Red Hat Bugzilla – Bug 1249113
kube-apiserver fails to start on boot due to network being unavailable
Last modified: 2017-11-14 17:31:22 EST
Description of problem:
During boot, the apiserver process may fail to start as it cannot bind to an IP address, resulting in this error:
Unable to find suitable network address.error='Unable to select an IP.' . Will try again in 5 seconds. Set the public address directly to avoid this wait.
This looks like a race condition where apiserver is trying to get a network address before the interface is ready. By enabling NetworkManager-wait-online.service, we never see kube-apiserver to fail on boot with this message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have NM control the NICs on the host
kube-apiserver will fail to start on boot (even after retrying several times), but can be started manually without issue.
kube-apiserver should start normally on boot with no manual intervention
*** Bug 1240563 has been marked as a duplicate of this bug. ***