You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.
The DISABLED_create_auxgateway_test testcase used to be NOT disabled, meaning that it will run automatically as one of the unit testcases.
However, in aca_CHILD container, which runs the unit tests before running the traffic tests, has the static ARP entries left after the unit tests. After running DISABLED_create_auxgateway_test, you can find the arp entries with this command:
docker exec aca_CHILD arp -n
and you should see that there's a MAC address of fa:17:3e:d7:f2:6d, if we don't clean this up, when we run the traffic tests(DISABLED_2_ports_CREATE_test_traffic_PARENT and DISABLED_2_ports_CREATE_test_traffic_CHILD), the issue #216 will happen.
If you install tcpdump on the aca_CHILD and aca_PARENT containers, and use this command to capture the packets, you will see above mac address associated with the wrong IP.
The text was updated successfully, but these errors were encountered:
er1cthe0ne
changed the title
Need proper cleanup for the static arp entries in DISABLED_create_auxgateway_test
[Zeta] Need proper cleanup for the static arp entries in DISABLED_create_auxgateway_test
Mar 9, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't workingZetaIntegration with Zeta
The DISABLED_create_auxgateway_test testcase used to be NOT disabled, meaning that it will run automatically as one of the unit testcases.
However, in
aca_CHILD
container, which runs the unit tests before running the traffic tests, has the static ARP entries left after the unit tests. After runningDISABLED_create_auxgateway_test
, you can find the arp entries with this command:and you should see that there's a MAC address of
fa:17:3e:d7:f2:6d
, if we don't clean this up, when we run the traffic tests(DISABLED_2_ports_CREATE_test_traffic_PARENT
andDISABLED_2_ports_CREATE_test_traffic_CHILD
), the issue #216 will happen.If you install tcpdump on the
aca_CHILD
andaca_PARENT
containers, and use this command to capture the packets, you will see above mac address associated with the wrong IP.The text was updated successfully, but these errors were encountered: