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
always collect containerd logs during e2e-node tests #95411
Conversation
containerd is almost always running, even below docker
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.
LGTM
logs!
looks like it works to me if you check the |
testing /test |
@MHBauer: The
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
nope, not in the list, looking for ci-kubernetes-node-kubelet-benchmark |
Given that I don't think it'll fail if the logs don't exist, it's less 'required' logs, and more 'collect by default' logs. |
/retest |
/assign @klueska |
Re: kubernetes/test/e2e_node/services/logs.go Line 76 in ee297b6
Is this still valid? It sounds like we want to move away from requiring runtime-specific logs from this comment? |
kubernetes/test/e2e_node/services/services.go Lines 165 to 174 in ee297b6
It does not matter. It does not fail if the log does not exist, so we might as well have a big list of desired logs. I can clean it up some more, since I am already in here. |
/lgtm |
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, MHBauer, oomichi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Review the full test history for this PR. Silence the bot with an |
containerd is almost always running, even below docker
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Instead of configuring all of the tests that use containerd to collect the containerd logs, it looks better to collect the containerd logs by default, as it is almost always running.
Which issue(s) this PR fixes:
Helping to debug tests.
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/cc @mikebrow
/assign @dims