Closed jackfrancis closed 5 years ago
kubelet is systemctl-enabled, as expected:
azureuser@k8s-agentpool1-29898149-vmss000000:~$ systemctl list-unit-files | grep kubelet
kubelet-monitor.service static
kubelet.service enabled
kubelet-monitor.timer disabled
This may be a regression due to #1073:
systemctl status kubelet
● kubelet.service - Kubelet
Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Thu 2019-04-18 18:42:20 UTC; 14min ago
Process: 1437 ExecStartPre=/sbin/sysctl -w net.netfilter.nf_conntrack_tcp_be_liberal=1 (code=exited, status=255)
Process: 1434 ExecStartPre=/bin/mount --make-shared /var/lib/kubelet (code=exited, status=0/SUCCESS)
Process: 1427 ExecStartPre=/bin/bash -c if [ $(mount | grep "/var/lib/kubelet" | wc -l) -le 0 ] ; then /bin/mount --bind /var/lib/kubelet /var/lib/kubelet ; fi (code=exited, statu
Process: 1425 ExecStartPre=/bin/mkdir -p /var/lib/cni (code=exited, status=0/SUCCESS)
Process: 1422 ExecStartPre=/bin/mkdir -p /var/lib/kubelet (code=exited, status=0/SUCCESS)
Process: 1418 ExecStartPre=/bin/bash /opt/azure/containers/kubelet.sh (code=exited, status=0/SUCCESS)
Apr 18 18:42:19 k8s-agentpool1-30831010-vmss000000 systemd[1]: kubelet.service: Unit entered failed state.
Apr 18 18:42:19 k8s-agentpool1-30831010-vmss000000 systemd[1]: kubelet.service: Failed with result 'exit-code'.
Apr 18 18:42:20 k8s-agentpool1-30831010-vmss000000 systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
Apr 18 18:42:20 k8s-agentpool1-30831010-vmss000000 systemd[1]: Stopped Kubelet.
Apr 18 18:42:20 k8s-agentpool1-30831010-vmss000000 systemd[1]: kubelet.service: Start request repeated too quickly.
Apr 18 18:42:20 k8s-agentpool1-30831010-vmss000000 systemd[1]: Failed to start Kubelet.
Apr 18 18:42:20 k8s-agentpool1-30831010-vmss000000 systemd[1]: kubelet.service: Unit entered failed state.
Apr 18 18:42:20 k8s-agentpool1-30831010-vmss000000 systemd[1]: kubelet.service: Failed with result 'start-limit-hit'.
Confirmed, will revert #1073.
Observed in a cluster built from master: