Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Kubernetes node e2e test fail (and flake) with recent master commit #5202

Closed
harche opened this issue Aug 16, 2021 · 6 comments
Closed

Kubernetes node e2e test fail (and flake) with recent master commit #5202

harche opened this issue Aug 16, 2021 · 6 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@harche
Copy link
Contributor

harche commented Aug 16, 2021

Description

Master branch of crio is very flaky with node e2e tests. While the commit 4d14fd61d2d533a0bb81557b54d3505be830efa7 and earlier are relatively stable provided the host is using runc v1.0.1

Steps to reproduce the issue:

  1. Run node e2e tests

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of crio --version:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):
@saschagrunert
Copy link
Member

As discussed earlier, I think #5113 is the suspicious PR introducing the breaking change.

@saschagrunert saschagrunert changed the title master branch is extremely flaky with node e2e Kubernetes node e2e test fail (and flake) with recent master commit Aug 16, 2021
@saschagrunert saschagrunert mentioned this issue Aug 16, 2021
Closed
@saschagrunert
Copy link
Member

A friendly reminder that this issue had no activity for 30 days.

@saschagrunert saschagrunert added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2022
@harche
Copy link
Contributor Author

harche commented Jun 28, 2022

We need to bump up the crio commit in upstream node e2e tests and see if they pass fine.

@saschagrunert saschagrunert mentioned this issue Jun 28, 2022
Merged
@saschagrunert
Copy link
Member

Let's give it a try in #6007

@saschagrunert saschagrunert removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2022
@saschagrunert saschagrunert mentioned this issue Jun 28, 2022
Closed
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 29, 2022
@github-actions
Copy link

Closing this issue since it had no activity in the past 90 days.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 28, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@saschagrunert @harche