-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1763700: kubelet: add dependency on network-online.target #1206
Bug 1763700: kubelet: add dependency on network-online.target #1206
Conversation
This fixes a race when the kubelet enumerates the hostname at startup. ref: https://bugzilla.redhat.com/show_bug.cgi?id=1763700
@rphillips: This pull request references Bugzilla bug 1763700, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
Also remember the installer has a copy of |
@rphillips: This pull request references Bugzilla bug 1763700, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Given Kube dependency on the hostname (something that'd be good to fix eventually but)...this makes sense. Did this really never come up before though? Do other people's |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @miabbott
The cloud provider in the kubelet will gather the hostname from the metadata service (ie, aws, etc). Namely, this PR fixes the issue with metal or other non-cloud based platforms. @cgwalters typhoon waits for the resolve.conf to get set [1], but I don't love the implementation. |
😱 There's another codebase doing that? |
@cgwalters same code base as the kubelet, but each cloud provider does the hostname detection slightly different [source]. |
/approve |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ashcrow, jlebon, kikisdeliveryservice, miabbott, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
@rphillips: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@rphillips: All pull requests linked via external trackers have merged. Bugzilla bug 1763700 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherrypick release-4.2 |
@runcom: new pull request created: #1212 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Recent changes[1] mean that critical services wait for NetworkManager-wait-online.service and the timeout has been increased[2] to 300 seconds which results in significant delays in booting instances while we wait for the second interface. 1 - openshift/machine-config-operator#1206 2 - https://bugzilla.redhat.com/show_bug.cgi?id=1741296
Recent changes[1] mean that critical services wait for NetworkManager-wait-online.service and the timeout has been increased[2] to 300 seconds which results in significant delays in booting instances while we wait for the second interface. 1 - openshift/machine-config-operator#1206 2 - https://bugzilla.redhat.com/show_bug.cgi?id=1741296
This was added in openshift#1206 to the base unit, but not the baremetal copy of this file
This was added in openshift#1206 to the base unit, but not the baremetal copy of this file
This was added in openshift#1206 to the base unit, but not the baremetal copy of this file
This was added in openshift#1206 to the base unit, but not the baremetal copy of this file
- What I did
This fixes a race when the kubelet enumerates the hostname at startup. Wait for the network-online.target to be ready before starting the Kubelet.
ref: https://bugzilla.redhat.com/show_bug.cgi?id=1763700
- How to verify it
- Description for the changelog