Comment 28 for bug 1545913

juju-core 2.0~beta3-0ubuntu3 and juju-core-1 1.25.4-0ubuntu5 have both been accepted into the Ubuntu archive. However, they are stalled in xenial-proposed because the juju-core autopkgtests have regressed (on amd64, i386, and ppc64el):

http://autopkgtest.ubuntu.com/packages/j/juju-core/xenial/amd64/

I know that the packaging delta from juju-core 1.25.0-0ubuntu3 included new "lxd" autopkgtests replacing the "local" autopkgtests, which makes sense. But these tests don't run, something was lost in translation from the old tests:

adt-run [16:49:12]: test current-lxd-provider: [-----------------------
+ sh debian/tests/normal-user.sh debian/tests/lxd-provider
+ adduser --disabled-password --gecos jujutest
adduser: Only root may add a user or group to the system.
adt-run [16:49:13]: test current-lxd-provider: -----------------------]

The old 'local' tests declared a dependency on sudo and declared that they needed to run as root. The new lxd test has dropped this information, and therefore fails as above.

Please see the logs linked at the above url for the full details on failures; the failure seems to be the same for all three failing tests (current-lxd-provider, current-manual-provider, future-lxd-provider) across all three affected archs (amd64, i386, ppc64el). Please test your fix with autopkgtest (e.g., 'adt-run -B --unbuilt-tree . --- adt-virt-$option') before reuploading to the archive.