Michael and I debugged this life in an affected instance, and we found the two problems:
* The LXD bridge needs to get added to no_proxy in /etc/environment or at least in the env where the test is run. Something like appending ",10.0.8.*" (this syntax needs to be tested, as $no_proxy is seriously underdocumented) * The ethernet interfaces in Scalingstack instances have an MTU of 1400, which breaks networking in containers. I recently added this gem to my armhf setup script (https://git.launchpad.net/~ubuntu-release/+git /autopkgtest-cloud/tree/tools/armf-lxd-slave.userdata#n98): lxc profile device remove default eth0 lxc profile device add default eth0 nic nictype=bridged parent=lxdbr0 mtu=1400 with these two changes we get very far, final tests pending. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571082 Title: autopkgtest lxd provider tests fail for 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1571082/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
