On Mon, Apr 18, 2016 at 11:16:44PM -0000, Tycho Andersen wrote: > Was there something else running on the box that might cause LXD to restart > while juju was bootstrapping?
Nope. Dedicated canonistack instance. The autopkgtest log output also shows this: adt-run [16:32:51]: test current-lxd-provider: [----------------------- + sh debian/tests/setup-lxd.sh + debconf-communicate 0 value set 0 value set 0 value set 0 value set 0 value set 0 value set 0 value set 0 value set 0 value set 0 value set 0 value set + rm -rf /etc/default/lxd-bridge + dpkg-reconfigure lxd --frontend=noninteractive Warning: Stopping lxd.service, but it can still be activated by: lxd.socket + systemctl start lxd-bridge So it looks like the test itself restarts lxd. But I should hope that 'systemctl start lxd-bridge' is synchronous and doesn't return until lxd is up and running? -- 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
