-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 race condition of deleting ccnp in e2e test #24484
Fix race condition of deleting ccnp in e2e test #24484
Conversation
41ed28e
to
1930c8f
Compare
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' hit: #20723 (85.78% similarity) |
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.
Nice find!
I believe the CI failure belongs to a known flake #20723, and I can't reproduce it by running locally. |
I agree. Feel free to mark ready-to-merge once it's reviewed and you have triaged CI failures with a comment. |
Let's keep 👀 on the HostFW flakes (eg. #22578) for a bit ... maybe this is all what was needed for them? @jschwinger233 we typically backport CI fixes. Could you check how far back this applies (I would assume |
There is a flake in e2e test when a test case starts to proceed before ccnp comes to take effect by cilium-agent. The correct way to delete ccnp is to run "kubectl delete" followed by "cilium policy wait", and kubectl helper already has such wrappers. Fixes: cilium#24380 Signed-off-by: Zhichuan Liang <gray.liang@isovalent.com>
There is a flake in e2e test when a test case starts to proceed before cnp comes to take effect by cilium-agent. The correct way to delete cnp is to run "kubectl delete" followed by "cilium policy wait", and kubectl helper already has such wrappers. Signed-off-by: Zhichuan Liang <gray.liang@isovalent.com>
1930c8f
to
a86ef7c
Compare
No-change push to split the content up into two patches, and CI passed previously. |
There is a flake in e2e test when a test case starts to proceed before ccnp/cnp comes to take effect by cilium-agent. The correct way to delete ccnp/cnp is to run "kubectl delete" followed by "cilium policy wait", and kubectl helper already has such wrappers.
Fixes: #24380