canonical-certification-server from checkbox-dev still won't run the iperf tests

$ canonical-certification-server --check-config
Configuration files:
 - /etc/xdg/plainbox.conf (not present)
 - /etc/xdg/checkbox.conf (not present)
 - /etc/xdg/canonical-certification.conf
 - /home/ubuntu/.config/plainbox.conf (not present)
 - /home/ubuntu/.config/checkbox.conf (not present)
 - /home/ubuntu/.config/canonical-certification.conf (not present)
Variables:
   welcome_text=Welcome to System Certification!

This application will gather information from your system. Then you will be asked manual tests to confirm that the system is working properly. Finally, you will be asked for the Secure ID of the computer to submit the information to the certification.canonical.com database.

To learn how to create or locate the Secure ID, please see here:

https://certification.canonical.com/home/ubuntu-certified
   default_provider=all
   secure_id=unset
   c3_url=https://certification.canonical.com/submissions/submit/
   fallback_file=unset
   whitelist=unset
Sections:
   environment={'TEST_TARGET_IPERF': '10.0.0.1', 'TEST_USER': 'anonymous', 'TEST_PASS': '', 'TEST_TARGET_FTP': 'your-ftp-server.example.com'}
No validation problems found

OK, there are two issues with the configuration (both are non-obvious, apologies, I'll see if there's a way to mitigate that). And an actual bug with the whitelist :)

First, the SECURE_ID setting needs to be lowercase, so:

[sru]
secure_id=mumblemumble

Second, the network script needs ALL values to be passed to it. Since you're leaving TEST_PASS blank, it'll probably not want to run correctly. Just set TEST_PASS to something (a@b.com is what I used in the old anonymous ftp days, if that's what you have).

I'll update the config file template to guide users through this set of finicky options.

And finally (Another action item here). On your system the network interfaces look like this:

path: /devices/pci0000:00/0000:00:1c.0/0000:05:00.0
bus: pci
category: NETWORK
driver: tg3
product_id: 5727
vendor_id: 5348
product: NetXtreme BCM5720 Gigabit Ethernet PCIe
vendor: Broadcom Corporation
interface: em1

Notice the interface name is em1, so the generated jobs will look like

ethernet/multi_nic_em1

however, the whitelist has this:
ethernet/multi_nic
ethernet/multi_nic_eth\d

So the subjobs will clearly not match and never run :(

This explains why my simplistic "it runs here!" verification was bogus since of course on my consumer-level equipment I have ethX interfaces. Also explains why "plainbox run -i ethernet/multi_nic_.*" worked, because I wasn't replicating the eth.* restriction.

I'll update the whitelist to better catch these network interface names.