-
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
CI: RuntimePrivilegedUnitTests: arping failed in TestArpPingHandling #14125
Comments
The test was recently introduced by #14070. |
I bumped this to daily flakes since I'm seeing it several times per day, just now in e.g. #14113. |
#14201 might fix this. |
@brb still happening |
Managed to reproduce it locally running in the loop, continuing investigation. |
Switching arping implementation to #13112 didn't resolve the issue. Also, I see with tcpdump that the arping response, which waiting times out according to the failure log, is received by the host. |
Tried running tests with strace for the whole day - no luck reproducing the issue. |
Happened again in https://jenkins.cilium.io/job/Cilium-PR-Runtime-4.9/3145/testReport/junit/(root)/Suite-runtime/RuntimePrivilegedUnitTests_Run_Tests/ for the same PR as ^^. |
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>
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>
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>
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]: cilium/cilium#14125 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
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]: cilium/cilium#14125 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
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]: cilium/cilium#14125 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
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]: cilium/cilium#14125 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
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]: cilium/cilium#14125 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
[ upstream commit 2284c76 ] 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>
[ upstream commit 2284c76 ] 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>
[ upstream commit 2284c76 ] 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) Co-authored-by: Tobias Klauser <tobias@cilium.io> Signed-off-by: Martynas Pumputis <m@lambda.lt>
[ upstream commit 2284c76 ] 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) Co-authored-by: Tobias Klauser <tobias@cilium.io> Signed-off-by: Martynas Pumputis <m@lambda.lt>
[ upstream commit 2284c76 ] 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>
https://jenkins.cilium.io/job/Cilium-PR-Runtime-4.9/2657/testReport/junit/(root)/Suite-runtime/RuntimePrivilegedUnitTests_Run_Tests/
372c1e59_RuntimePrivilegedUnitTests_Run_Tests.zip
The text was updated successfully, but these errors were encountered: