New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix and add more commands in CI sysdumps #16721
Conversation
When using journalctl to read the logs of another system, one need to explicitly pass -D and the directory containing the logs to successfully read the log messages. Fixes: a9285f4 ("[CI] Move vagrant start script to separate file") Signed-off-by: André Martins <andre@cilium.io>
cilium/log-gatherer:v1.1 is not mutable thus we don't need to always performing a pull of that docker image from docker hub. Fixes: a9285f4 ("[CI] Move vagrant start script to separate file") Signed-off-by: André Martins <andre@cilium.io>
To help debug certain flakes, we need kube-apiserver logs available in the test sysdump. This commit adds the ability to retrieve such logs. Signed-off-by: André Martins <andre@cilium.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more thing missing in CI 3.0 I guess. Could we collect those in sysdumps as well?
Collecting apiserver logs in generic sysdump is a bit tricky because we have no guarantee of where the apiserver is running; it's commonly not even part of the cluster (eg managed k8s environments like EKS, GKE, etc.). |
In order to further debug #16720 we need to retrieve kube-apiserver logs which is being added by this PR.
Fixes #14293