Troubleshooting Checklist

use this topic as a checklist for troubleshooting issues with the swimlane platform installer (spi) check the configuration ensure that docker and kubelet are running containerd run systemctl status containerd if the service is in a failed state, search the service log for errors with this command journalctl fu containerd kubelet run systemctl status kubelet if the service is in a failed state, search the service log for errors with this command journalctl fu kubelet check cluster node health run kubectl get nodes all nodes should show ready in the status column if any nodes are not showing as ready , run the following and look for relevant issues/errors kubectl describe node nodename check for any pods that are not running run kubectl get pods a | grep v running | grep v completed if any pods are listed check the pod logs for issues with this command kubectl logs all containers podname n namespace check the pod describe output for issues with this command kubectl describe pod podname n namespace check for errors in the events run kubectl get events sort by= metadata creationtimestamp ensure the infrastructure is configured according to the docid 9lxricxlm1t14ydlkt4zr or docid\ snkpyftncien7nwfs7tfp resources to check; logs/info to retrieve ensure that there is a support bundle available see docid\ qmv6 xfrfeuey9d5wybkc for details in addition to the support bundle, get the status and logs of the containerd and kubelet services use this code for services in containerd kubelet; do echo $services ; systemctl is active $services ; systemctl is enabled $services ; echo ""; done ``` ``` for services in containerd kubelet; do echo $services ; systemctl status $services ; systemctl status $services ; echo ""; done ``` ``` journalctl u kubelet since "3 hour ago" > /tmp/kubelet \<node name> log txt journalctl u containerd since "3 hour ago" > /tmp/containerd \<node name> log txt if you can't generate a support bundle, for example, if the issue is occurring before the spi is successfully installed and running, or the support bundle generation fails, then run the following commands and provide the output kubectl get pods a | grep v running | grep v completed if any pods are listed, include the pod logs with kubectl logs all containers podname n namespace include the pod describe output with kubectl describe pod podname n namespace then continue providing output with kubectl get pods a kubectl get deploy a kubectl get sts a kubectl get pvc a kubectl get pv a kubectl get svc a kubectl get nodes if any nodes have a status other than ready , then also include the describe output of the node with kubectl describe node nodename kubectl get events sort by= metadata creationtimestamp next, get the status and logs of the containerd and kubelet services for services in containerd kubelet; do echo $services ; systemctl is active $services ; systemctl is enabled $services ; echo ""; done for services in containerd kubelet; do echo $services ; systemctl status $services ; systemctl status $services ; echo ""; done journalctl u kubelet since "3 hour ago" > /tmp/kubelet \<node name> log txt journalctl u containerd since "3 hour ago" > /tmp/docker \<node name> log txt finally, provide the following os and version infrastructure setup instance provider, for example, bare metal, vm, aws instance, azure instance, gcp instance, etc instance sizes, including memory, cpu, disk/partitions load balancer type and setup