-
Notifications
You must be signed in to change notification settings - Fork 40.9k
Improve containers lifecycle test output parsing #132485
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
Improve containers lifecycle test output parsing #132485
Conversation
/test pull-kubernetes-node-kubelet-serial-crio-cgroupv2 |
/priority important-soon |
/hold Have to look into this again. |
/test pull-kubernetes-node-kubelet-serial-crio-cgroupv2 |
This should fix the following test when running it with CRI-O: ``` [It] [sig-node] [Feature:SidecarContainers] [Serial] Containers Lifecycle when A node running restartable init containers reboots should restart the containers in right order with the proper phase after the node reboot ``` The issue is that we have prefixed "unable to retrieve container logs for …" outputs in the message to be parsed. We now skip that part and leave the current behavior untouched. Signed-off-by: Sascha Grunert <[email protected]>
c295375
to
0028ea8
Compare
/test pull-kubernetes-node-kubelet-serial-crio-cgroupv2 |
Tests are green now /unhold |
/lgtm |
LGTM label has been added. Git tree hash: 2d5ab4246fb07c74e8b047e6477fd359d9bdfb9e
|
/approve thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ffromani, saschagrunert 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 |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
This should fix the following test when running it with CRI-O:
The issue is that we have prefixed "unable to retrieve container logs for …" outputs in the message to be parsed. We now skip that part and leave the current behavior untouched.
Which issue(s) this PR is related to:
Refers to #131184
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: