-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
bpf: update dsr flag properly #18041
Conversation
/test Job 'Cilium-PR-K8s-1.22-kernel-4.19' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment Job 'Cilium-PR-K8s-1.21-kernel-5.4' hit: #17353 (89.67% similarity) |
/test |
test-1.22-4.19 |
/test-1.22-4.19 |
@pchaigno Hello, could you recheck this commit please. IMO, based on the logs of failed tests, I don’t think my PR was the cause of these problems. |
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.
Thanks for the PR!
A few comments. Also, could you improve the commit msg. In particular, it should describe the problem your commit tries to solve, and then briefly discuss the solution.
I've checked the CI failures - all of them are flakes and unrelated to your changes.
121f969
to
076ffb8
Compare
@brb, Hello. Here you are, I update the commit msg and describe the problem and the solution. |
@Inode1 Thanks for the updated commit msg. |
076ffb8
to
4ff832e
Compare
/test Job 'Cilium-PR-K8s-1.21-kernel-5.4' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
/test |
test-gke Job 'Cilium-PR-K8s-GKE' hit: #18218 (92.43% similarity) |
@brb, Hello. There are several failed tests, is it somehow connected with my PR? Do you need any help from me? |
The test failures are unrelated (#18218). Marking as ready to merge. |
@Inode1 Thanks for your contribution :) Merging the PR. |
Thanks, good news. |
I reproduced this issue and after this patch new tcp sessions with dsr flag update the already created entries in the conntrack table.
Fixes: #17759