Comment 4 for bug 1367584

OK, the logic is as follows, assuming plainbox is used for the installation (--plainbox when using launch_testrun):

- if -p is given, it will use the sru whitelist (I think this is not the problem here)
- If -p is not given:
   - If the whitelist is client-cert-12-04-4.whitelist, it will be configured
      /usr/share/2013.com.canonical.certification:certification-client/whitelists/client-cert-12-04-4.whitelist
   - If the whitelist is something else, it will be configured from /usr/share/2013.com.canonical.certification:checkbox/whitelists/$WHITELIST_NAME
  - If whitelist is not given, it will default to using client-cert.whitelist.

We can remove the part of the preseed that sets the bad whitelist. For this I'd appreciate if you could tell me which whitelist is being set up, and how you are calling launch_testrun.

As a workaround, as you noted, you can manually comment the whitelist entry in the config file before starting the tests. Please let me know if the workaround helps.