Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kubelet.service not waiting for network-online.target #1248

Closed
rosti opened this issue Apr 22, 2020 · 4 comments
Closed

kubelet.service not waiting for network-online.target #1248

rosti opened this issue Apr 22, 2020 · 4 comments
Assignees
@rosti
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@rosti
Copy link
Contributor

rosti commented Apr 22, 2020

Whenever kubeadm detects a system that has systemd-resolved running, it would provision the kubelet on the local node with a resolv.conf overwrite - /run/systemd/resolve/resolv.conf.

However, some kubeadm users have discovered an issue during system boot. The kubelet can end up in a race with the systemd-resolved service and actually startup loads with empty or incorrect resolve.conf files.

The race is caused by the fact that the kubelet.service file does not indicate dependence on the network-online.target.

xref kubernetes/kubeadm#2111

/kind bug
/assign
@rosti rosti added area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Apr 22, 2020
@neolit123
Copy link
Member

/priority important-longterm
cc @BenTheElder @aojea

@k8s-ci-robot k8s-ci-robot added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed needs-priority labels Apr 22, 2020
@rosti rosti mentioned this issue Apr 22, 2020
Merged
@BenTheElder
Copy link
Member

Thanks for the heads up, the resolv.conf in kind isn't systemd managed though.

I could definitely see this being an issue in prod systems 😬

@justaugustus justaugustus mentioned this issue Apr 24, 2020
Merged
@justaugustus
Copy link
Member

Closed via #1250.
/close

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closing this issue.

In response to this:

Closed via #1250.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rosti rosti

Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@neolit123 @justaugustus @BenTheElder @rosti @k8s-ci-robot