-
Notifications
You must be signed in to change notification settings - Fork 85
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
aarch64 flake: iptables - port forwarding ipv4 - sctp #433
Comments
now seen with tcp as well, https://cirrus-ci.com/task/4785774147665920 |
failed several times in the nightly cron job as reported by @lsm5: https://cirrus-ci.com/task/6728664411275264 |
Happened twice in a row again on yesterday's netavark/main Cirrus-Cron job. Always aarch64 (running on AWS). |
Luap99
added a commit
to Luap99/netavark
that referenced
this issue
Mar 7, 2023
I am not not 100% sure because I was unable to reproduce even with hack/get_ci_vm.sh. This flakes permanently in CI so there must be a different in the environment which causes it. However looking at the code we spawn the nc listener in the background so there is no guarantee that it will already listen when we make the nc connect call. To fix this we use the wait_for_port logic to ensure the port is bound. For now there is no sctp support, the /proc file format for it is completely different and I didn't want to spend more time on it so I just added a sleep and call it good enough. Fixes containers#433 Signed-off-by: Paul Holzinger <[email protected]>
Merged
Luap99
added a commit
to Luap99/netavark
that referenced
this issue
Mar 9, 2023
I am not not 100% sure because I was unable to reproduce even with hack/get_ci_vm.sh. This flakes permanently in CI so there must be a different in the environment which causes it. However looking at the code we spawn the nc listener in the background so there is no guarantee that it will already listen when we make the nc connect call. To fix this we use the wait_for_port logic to ensure the port is bound. For now there is no sctp support, the /proc file format for it is completely different and I didn't want to spend more time on it so I just added a sleep and call it good enough. Fixes containers#433 Signed-off-by: Paul Holzinger <[email protected]>
flouthoc
pushed a commit
to flouthoc/netavark
that referenced
this issue
Apr 24, 2023
I am not not 100% sure because I was unable to reproduce even with hack/get_ci_vm.sh. This flakes permanently in CI so there must be a different in the environment which causes it. However looking at the code we spawn the nc listener in the background so there is no guarantee that it will already listen when we make the nc connect call. To fix this we use the wait_for_port logic to ensure the port is bound. For now there is no sctp support, the /proc file format for it is completely different and I didn't want to spend more time on it so I just added a sleep and call it good enough. Fixes containers#433 Signed-off-by: Paul Holzinger <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have seen this twice now, just filling this as issue so we can keep track.
https://cirrus-ci.com/task/5590240982204416
https://cirrus-ci.com/task/6384006940852224
The text was updated successfully, but these errors were encountered: