juju test suite should be isolated and do 0 outbound network requests

[William Reade]

http://paste.ubuntu.com/6178801/

Well, I see how, but not how the code landed like that. Skipping them for now.

[John A Meinel (jameinel)]

The code worked before because there wasn't anything in the public s3 bucket for simplestreams data.

Then we uploaded the 1.15 release, and the permissions were wrong, so it searched and some tests started failing. We fixed the permissions, and now the tests that were running are seeing real data and failing.

[John A Meinel (jameinel)]

Note that I don't think we'll actually block a 1.16 release on fixing it. It *is* important for our ongoing development work, but as it is a test-suite issue not a user-facing issue it isn't a release blocker.

[John A Meinel (jameinel)]

We've landed what we need for 1.16 on this, but we need to have some time to ensure our test suite doesn't try to dial a remote machine. That doesn't need to block a release, though, because in production we really do want it to dial out :).

[Andrew Wilkins (axwalk)]

I think it'd be a good idea to block outbound network access on the bot, to prevent these things in the future. We can do this with something like:

    sudo unshare -n bash <<EOF
    ifconfig lo up
    su - $SUDO_USER -c "make check"
    EOF