-
Notifications
You must be signed in to change notification settings - Fork 366
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
[Flaky test] TestVLANNetwork failing #6023
Comments
Hey @antoninbas, wd like to know more how did you produce it. I tried, it has shown different errors on |
This failure was observed in CI. You should be able to reproduce it locally by running |
@antoninbas I tried running it locally a few times and it passes ok.
|
hey @shikharish, its actually failing in |
@shikharish Looking at the Github Actions history for Kind jobs on the main branch, I see that it failed twice out of the last 3 runs:
However, these failures are not always straightforward to reproduce locally. |
For VLAN Secondary Network e2e tests, we need to wait for secondary IPs to be available. Interface creation can take up to a few seconds after the Pod is in the Running state, as it happens asynchronously. Otherwise we can get the following error: secondary_network_test.go:194: Error when pinging between interfaces: interface eth1 not found on vlan-pod2. err: <nil> Fixes antrea-io#6023 Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
I got lucky, I was able to reproduce on my first try :) I submitted a PR to fix it |
For VLAN Secondary Network e2e tests, we need to wait for secondary IPs to be available. Interface creation can take up to a few seconds after the Pod is in the Running state, as it happens asynchronously. Otherwise we can get the following error: secondary_network_test.go:194: Error when pinging between interfaces: interface eth1 not found on vlan-pod2. err: <nil> Fixes antrea-io#6023 Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
For VLAN Secondary Network e2e tests, we need to wait for secondary IPs to be available. Interface creation can take up to a few seconds after the Pod is in the Running state, as it happens asynchronously. Otherwise we can get the following error: secondary_network_test.go:194: Error when pinging between interfaces: interface eth1 not found on vlan-pod2. err: <nil> Fixes #6023 Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
Describe the bug
I have observed the following test failure.
The text was updated successfully, but these errors were encountered: