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. This is also blocking several other related packages from migrating to xenial for release (closure, bigdata, openstack). I have attempted to get a clean baseline locally with the autopkgtests, using the adt-virt-ssh backend (to a xenial amd64 VM) to avoid any problems with nested lxd or otherwise. The current-lxd-provider test failed for me as follows: 2016-04-16 21:51:33 DEBUG juju.provider.lxd environ_broker.go:126 LXD requires https://, using: https://cloud-images.ubuntu.com/releases/ 2016-04-16 21:51:33 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD remote "default cloud images": "https://streams.canonical.com/juju/images/releases/"; 2016-04-16 21:51:33 INFO juju.tools.lxdclient client_image.go:129 no image for ubuntu-xenial found in https://streams.canonical.com/juju/images/releases/ 2016-04-16 21:51:33 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD remote "default ubuntu cloud images": "https://cloud-images.ubuntu.com/releases/"; 2016-04-16 21:51:34 INFO juju.tools.lxdclient client_image.go:135 found image from https://cloud-images.ubuntu.com/releases/ for xenial = 6cb0ba80a5fe32357568a473cbaf69f14d26da0ba6b08f5b1bcde7053fc73757 2016-04-16 21:51:34 INFO juju.tools.lxdclient client_image.go:147 copying image for ubuntu-xenial from https://cloud-images.ubuntu.com/releases/: 1% [...] copying image for ubuntu-xenial from https://cloud-images.ubuntu.com/releases/: 2016-04-16 21:51:37 INFO juju.tools.lxdclient client_image.go:147 copying image for ubuntu-xenial from https://cloud-images.ubuntu.com/releases/: 100% copying image for ubuntu-xenial from https://cloud-images.ubuntu.com/releases/: 2016-04-16 21:51:38 DEBUG juju.tools.lxdclient client_image.go:139 dropped 0 progress messages 2016-04-16 21:51:38 DEBUG juju.service discovery.go:59 discovered init system "systemd" from series "xenial" 2016-04-16 21:51:38 DEBUG juju.provider.lxd environ_broker.go:223 LXD user data; 1342 bytes 2016-04-16 21:51:38 INFO juju.provider.lxd environ_broker.go:201 starting instance "juju-b43656cd-a9d3-4c92-80ac-599997219ad7-machine-0" (image "ubuntu-xenial")... 2016-04-16 21:52:04 INFO juju.provider.common destroy.go:22 destroying model "admin" 2016-04-16 21:52:04 INFO juju.provider.common destroy.go:33 destroying instances 2016-04-16 21:52:04 INFO juju.provider.common destroy.go:53 destroying storage 2016-04-16 21:52:04 ERROR cmd supercommand.go:448 failed to bootstrap model: cannot start bootstrap instance: exit status 2 adt-run [14:52:05]: test current-lxd-provider: -----------------------] adt-run [14:52:06]: test current-lxd-provider: - - - - - - - - - - results - - - - - - - - - - current-lxd-provider FAIL non-zero exit status 1 If I could get this test to pass locally, I would go ahead with letting juju-core 2.0 in as-is and trust that the test incompatibilities with the autopkgtest infrastructure would be sorted out in short order. As it stands, however, I cannot be sure that this failure represents a buggy test, vs. a possibly serious problem in juju-core 2. So for the moment I'm leaving the package in -proposed. ** Changed in: juju-core (Ubuntu) Importance: Undecided => Critical ** Changed in: juju-core (Ubuntu) Status: New => Triaged -- 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
