this is probably caused from a human error, someone have started
dhclient manually. I'm closing this, sorry for the noise
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
At some point the dhcp client seems to try to search dhcp servers on all
interfaces (es calico, and docker interfaces), and start and stop
systemd-resolved very frequently:
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Stopping Network Name Resolution...
Stopped
** Summary changed:
- systemd-resolved service reach start-limit-hit if dhcp is not reachable of a
while
+ systemd-resolved service reach start-limit-hit if dhcp is not reachable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi there,
i have found my kubernetes worker in "NotReady" state with message "PLEG is not
healthy: pleg was last seen active" because dns resolution was not available
anymore because "systemd-resolved" service was not able to restart after DHCP
was not available for some
