-
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
arp: Add retries to arping #14601
arp: Add retries to arping #14601
Conversation
test-me-please |
retest-4.19 |
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.
After fixing the requested changes I would suggest to just run 1 more time the runtime CI since the test was faulty in there.
cbb040e
to
612d41f
Compare
It has been observed that sometimes arping fails with "i/o timeout". Further investigation [1] has shown that this happen due to the kernel not sending packets. Therefore, to mitigate the issue,try multiple times to send the request if the timeout error is encountered. [1]: #14125 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
Previously all tests were green. Pushed only a comment change. Retrying the runtime suite to see whether the flake is not reintroduced. |
test-runtime |
1 similar comment
test-runtime |
@aanm Ran the test 3 times - all passed. |
Once cilium/arping#6 has been merged, I will manually backport to v1.8 and v1.9. |
It has been observed that sometimes arping fails with "i/o timeout".
Further investigation [1] has shown that this happen due to the kernel
not sending packets. Therefore, to mitigate the issue, try multiple times
to send the request if the timeout error is encountered.
[1]: #14125 (comment)
Currently, I'm not labeling it for backporting to v1.{8,9}, as I've opened a discussion whether we could backport the arp library too which would significantly reduce complexity of arping-related backports.