This bug was fixed in the package juju-core - 2.0~beta6-0ubuntu1.16.04.1
---
juju-core (2.0~beta6-0ubuntu1.16.04.1) xenial-proposed; urgency=medium
* New upstream release 2.0-beta6 (LP: #1573176).
* Includes fixes for upstream bugs:
- juju loses agents during a lxd deploy.
Also tested on a separate system utilizing conjure-up and juju beta6 and
saw no agent lost errors for bug 1572237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573176
Title:
[SRU] Juju 2.0 for
I tested the package version 2.0~beta6-0ubuntu1.16.04.1 from xenial-
proposed and can verify that bug 1572237 is fixed in that package.
As when testing that bug, I used juju and conjure-up to deploy openstack
onto lxd containers. I saw no agent-lost errors.
** Tags removed: verification-needed
Hello Nicholas, or anyone else affected,
Accepted juju-core into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/2.0~beta6-0ubuntu1.16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
** Description changed:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU post-
- xenial release. This updates juju to the lastest 2.0 milestone version,
- beta5.
-
+ xenial release. This updates juju to
** Summary changed:
- [SRU] Juju 2.0 beta5 for Xenial
+ [SRU] Juju 2.0 for Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573176
Title:
[SRU] Juju 2.0 for Xenial
To manage notifications
