kubelet service stopped producing logs

Bug #1937335 reported by Syed Mohammad Adnan Karim
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Worker Charm
New
Undecided
Unassigned

Bug Description

While troubleshooting consul not working on the cluster, the customer found that the kubelet service was not producing any new logs on it and had to restart it to produce new logs.

The customer has 3 worker nodes dedicated to running consul.

I have attached a tarball containing the following:
snap.kubelet.daemon.service.log # journalctl output
snap.kube-proxy.daemon.service # journalctl output
kubectl-describe-pod-consul-0.out # kubectl describe pod consul-0 output

Revision history for this message
Syed Mohammad Adnan Karim (karimsye) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.