Collect logs for dead kubelets too

Collect logs via journalctl if journalctl is installed, rather than only if kubelet.service is running. The old way resulted in us losing logs any time the kubelet was failing. This, of course, breaks on a node if someone decided to install journalctl but not use it. But that is not the case on any of the images used by cluster-level tests at present.

Collect logs for dead kubelets too
773dbde0 · Michael Taufen · 85ff5559 · 773dbde0
Commit 773dbde0 authored Nov 29, 2016 by Michael Taufen
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

log-dump.sh cluster/log-dump.sh +1 -1

No files found.
--- a/cluster/log-dump.sh
+++ b/cluster/log-dump.sh
@@ -131,7 +131,7 @@ function save-logs() {
      esac
    fi

-    if log-dump-ssh "${node_name}" "sudo systemctl status kubelet.service" &> /dev/null; then
+    if log-dump-ssh "${node_name}" "command -v journalctl" &> /dev/null; then
        log-dump-ssh "${node_name}" "sudo journalctl --output=short-precise -u kube-node-installation.service" > "${dir}/kube-node-installation.log" || true
        log-dump-ssh "${node_name}" "sudo journalctl --output=short-precise -u kube-node-configuration.service" > "${dir}/kube-node-configuration.log" || true
        log-dump-ssh "${node_name}" "sudo journalctl --output=cat -u kubelet.service" > "${dir}/kubelet.log" || true