-
Notifications
You must be signed in to change notification settings - Fork 406
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
Missing systemctl daemon-reload after nodeip-configuration.service #2375
Comments
/cc @bcrochet |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. 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. |
You miss a daemon reload here:
machine-config-operator/templates/common/on-prem/units/nodeip-configuration.service.yaml
Line 31 in a060922
The service runs on purpose before kubelet:
With the goal to refresh nodeip information. The info is then written by the container into:
/etc/systemd/system/kubelet.service.d/20-nodenet.conf
But if IP addresses changed, without a daemon-reload, the new IP configuration will not be read by systemd.
See https://bugzilla.redhat.com/show_bug.cgi?id=1922812 for further details.
The text was updated successfully, but these errors were encountered: