[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

** Project changed: juju-core => juju -- 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:

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

I added an infrastructure-level workaround for bug 1572026, so you can drop this workaround from the juju-core test again: -- debian/tests/setup-lxd.sh 2016-04-19 09:21:40 + +++ debian/tests/setup-lxd.sh 2016-04-19 13:33:51 + @@ -23,9 +23,5 @@ dpkg-reconfigure lxd

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

** Changed in: juju-core Status: Triaged => Fix Released -- 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

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

This bug was fixed in the package juju-core - 2.0~beta4-0ubuntu2 --- juju-core (2.0~beta4-0ubuntu2) xenial; urgency=medium * Update debian/tests/ to work in the production network environment (LP: #1571082). -- Michael Hudson-Doyle Tue, 19 Apr

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

We figured out the patches for this, tests are now passing in production, and Michael will upload a new package momentarily. ** Changed in: juju-core (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

I filed bug 1572026 to track the issue about the lxdbr0 MTU. -- 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

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

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

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

This is the full log including a package build from https://code.launchpad.net/~mwhudson/ubuntu/xenial/juju/mwhudson r111. It fails on the same issue as above: 2016-04-19 06:39:08 ERROR cmd supercommand.go:448 Get https://10.0.8.1:8443/1.0/profiles: Forbidden ** Attachment added: "autopkgtest

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

I tried to run just the tests from https://code.launchpad.net/~mwhudson/ubuntu/xenial/juju/mwhudson on the production infra, and they still fail with 2016-04-19 06:14:49 ERROR cmd supercommand.go:448 Get https://10.0.8.1:8443/1.0/profiles: Forbidden I'll re-run this with building the source

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

To be certain, I fixed that problem (pushed my branch to https://code.launchpad.net/~mwhudson/ubuntu/xenial/juju/mwhudson) and ran the test suite again and it passed. So I don't feel like I've necessarily been very productive today, but the tests do actually pass, so maybe things can proceed? The

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

Oh the manual provider tests are broken by the change in Steve's branch to pass --system to adduser, resulting in the jujutest user having /bin/false for a shell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

So to be more confusing I ran the tests from https://code.launchpad.net/~vorlon/ubuntu/xenial/juju/test-improvements (which is just a single simple rev ahead of Martin's branch) on ec2 using adt-virt-null and locally using adt-virt-qemu and got different results: $ adt-run

Re: [Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

On Mon, Apr 18, 2016 at 11:16:44PM -, 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

Re: [Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

Thanks, Steve. On Mon, Apr 18, 2016 at 10:59:37PM -, Steve Langasek wrote: > Tycho, > > lxd logs attached. > > ** Attachment added: "1571082-lxd-logs.tar.xz" > > https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1571082/+attachment/4639541/+files/1571082-lxd-logs.tar.xz

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

Tycho, lxd logs attached. ** Attachment added: "1571082-lxd-logs.tar.xz" https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1571082/+attachment/4639541/+files/1571082-lxd-logs.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

Hi Steve, On the off chance you still have the machine you used as the backend for your adt run laying around, can you post the contents of /var/log/lxd somewhere? It looks to me like it never actually hit LXD, but let's just check to be sure. -- You received this bug notification because you

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

** Tags added: jujuqa -- 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:

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

Not sure if this is the same issue, but I get a hang locally with "adt- run --apt-pocket=proposed -U juju-core --- qemu adt-xenial- amd64-cloud.img". The last thing that I see is: adt-run [11:33:28]: test current-lxd-provider: [--- [...] 2016-04-18 09:34:36 INFO

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

I have some changes from Friday to address these test failures and the armhf one, that I've now committed and put in the packaging branch: As the lxd changes

[Bug 1571082] Re: autopkgtest lxd provider tests fail for 2.0

With less than a week to go to 16.04 release date, the status is: - juju-core-1 is in xenial - juju-core 1.25 is also in xenial - juju-core 2 is blocked in xenial-proposed because of test failures. This situation is clearly not releasable; we need to get juju-core 2 into xenial for release.