Ethernet tests ethernet/iperf3_{interface}

[pieqq]

Bug Description

ethernet/iperf3_{interface} job runs the network.py script that toggles network interfaces before and after the test.

Sometimes, this does not work; recently, we've got issues with 2 customer projects:

• in the first, a CANBus interface is declared. It is down by default because it is not plugged to anything, and we only plug it during the CANBus test. When ethernet/iperf3_{interface} jobs are run, it tries to up the CANBus interface, fails and complains
• in the other one, a virtual network is present, and, similarly, is down by default (and cannot be activated). It results in the following complaints from the script:

WARNING:root:Removing iperf server 10.102.182.100 (10.102.182.100) from
WARNING:root:test list since it's not within 10.102.88.0/23.
WARNING:root:Removing iperf server 10.102.182.137 (10.102.182.137) from
WARNING:root:test list since it's not within 10.102.88.0/23.
WARNING:root:Removing iperf server 10.102.182.101 (10.102.182.101) from
WARNING:root:test list since it's not within 10.102.88.0/23.
INFO:root:Testing enp1s0 against 10.102.89.198
INFO:root:Have successfully pinged 10.102.89.198 on enp1s0
INFO:root:-------------------- Test Run Number 1 --------------------
INFO:root:Using 1 thread.
INFO:root:Connecting to port 5201 on server....
INFO:root:Avg Transfer speed: 939.1 Mb/s
INFO:root:93.91% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 3.0%
INFO:root:
INFO:root:-------------------- Test Run Number 2 --------------------
INFO:root:Using 1 thread.
INFO:root:Connecting to port 5201 on server....
INFO:root:Avg Transfer speed: 939.3 Mb/s
INFO:root:93.93% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 2.9%
INFO:root:
INFO:root:-------------------- Test Run Number 3 --------------------
INFO:root:Using 1 thread.
INFO:root:Connecting to port 5201 on server....
INFO:root:Avg Transfer speed: 939.1 Mb/s
INFO:root:93.91% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 2.9%
INFO:root:
INFO:root:-------------------- Test Run Number 4 --------------------
INFO:root:Using 1 thread.
INFO:root:Connecting to port 5201 on server....
INFO:root:Avg Transfer speed: 939.1777777777778 Mb/s
INFO:root:93.92% of theoretical max 1000 Mb/s
INFO:root:Average CPU utilization: 3.0%
INFO:root:
RTNETLINK answers: Invalid argument
ERROR:root:Failed to restore enp0s30f4:Command '['ip', 'link', 'set', 'dev', 'enp0s30f4', 'up']' returned non-zero exit status 2.
RTNETLINK answers: Invalid argument
ERROR:root:Failed to restore enp0s30f5:Command '['ip', 'link', 'set', 'dev', 'enp0s30f5', 'up']' returned non-zero exit status 2.

Maybe a better way would be to save the status of each interface before the test, and bring all the interfaces in the same status after the test (i.e. to not touch interfaces that are down at the beginning of the test).

To Reproduce

1. Make sure the device you're testing has network interfaces that are down and cannot be brought up.
2. Ensure that checkbox config contains the IP# for the iperf3 server
3. Select the stress test plan for 22.04 desktop
4. Select the Ethernet tests under this test plan.

Environment

• OS: 22.04
• Checkbox 2.0.0

Relevant log output

No response

Additional context

No response

[pieqq]

Duplicate of #233