As part of the cloud suite we disable DUT internet access by disabling ipv4 port forwarding on the worker. We were disabling it before provisioning the DUT. This caused problems on the jetson orin devices, where we may have to build a jetson-flash docker container during provision time - the build container would have no internet access and fail to build.
So I moved it to after the DUT is provisioned, but just before we power it on. I also added to the teardowns to re-enable it - in case we end up with a test failure in between disabling and re-enabling it - as this would cause it to be disabled for subsequent tests, and the DUT would not have internet access.
In a separate leviathan worker PR - I have integrated enabling port forwarding in the network set up, to avoid accidents like this again - each test run we'll ensure it is enabled
acostach
commented
7 months ago
As part of the cloud suite we disable DUT internet access by disabling ipv4 port forwarding on the worker. We were disabling it before provisioning the DUT. This caused problems on the jetson orin devices, where we may have to build a jetson-flash docker container during provision time - the build container would have no internet access and fail to build.
So I moved it to after the DUT is provisioned, but just before we power it on. I also added to the teardowns to re-enable it - in case we end up with a test failure in between disabling and re-enabling it - as this would cause it to be disabled for subsequent tests, and the DUT would not have internet access.
In a separate leviathan worker PR - I have integrated enabling port forwarding in the network set up, to avoid accidents like this again - each test run we'll ensure it is enabled
Change-type: patch