RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):

atomic 7.1.3-1
kubernetes-0.17.1-4.el7


How reproducible:
Reliably


Steps to Reproduce:
1. Have NM control the NICs on the host
2. Reboot
3.

Actual results:
kube-apiserver will fail to start on boot (even after retrying several times), but can be started manually without issue.

Expected results:
kube-apiserver should start normally on boot with no manual intervention

Additional info:

*** Bug 1240563 has been marked as a duplicate of this bug. ***

As of Red Hat Enterprise Linux 7.5, the kubernetes packages shipped in the RHEL Extras channel are deprecated, and Red Hat no longer supports the manual installation and configuration of kubernetes on RHEL. OpenShift Container Platform is Red Hat’s fully supported distribution of Kubernetes.