TEST_TARGET_IPERF still not being passed to nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Testflinger |
New
|
Undecided
|
Unassigned |
Bug Description
Recently Paul updated the server nodes to include TEST_TARGET_IPERF:
https:/
however it still seems this is not being provided in a manner that checkbox remote can consume.
SO the config is Testflinger, using checkbox-remote.
In case this is an issue with the job description, the failing jobs are template created using this template job:
95 unit: template
96 template-resource: device
97 template-filter: device.category == 'NETWORK' and device.interface != 'UNKNOWN'
98 plugin: shell
99 category_id: com.canonical.
100 id: ethernet/
101 _summary: Multi-NIC Iperf3 SRU testing for NIC {interface}
102 estimated_duration: 1200.0
103 requires:
104 executable.name == 'iperf3'
105 executable.name == 'ethtool'
106 executable.name == 'nmap'
107 user: root
108 environ: TEST_TARGET_IPERF
109 command: network.py test -i {interface} -t iperf --iperf3 --scan-timeout 3600 --fail-threshold 80 --cpu-load-
110 _description:
111 This is a shorter SRU version of the standard iperf3 based network test for
112 servers. It is intended to ONLY be used for SRU and is not valid for offical
113 certification.
This template is a mirror of the non-SRU job called
81 id: ethernet/
with the only difference being it's a shorter run.
When the actual job runs
https:/
it appears that TEST_TARGET_IPERF is not being passed to the script as the output looks like this:
WARNING:root:Test server (0.0.0.0) is NOT within 10.245.128.0/22
WARNING:root:This may cause test issues