This bug was fixed in the package juju-core - 1.16.3-0ubuntu0.13.10.1
---------------
juju-core (1.16.3-0ubuntu0.13.10.1) saucy-proposed; urgency=low
* New upstream stable point release:
- MAAS: juju destroy-environment also destroys nodes that are not
controlled by juju/in different juju environments
(LP: #1229275, #1081247).
- MAAS: LXC container provisioning broken due to missing secrets
in API calls (LP: #1246556).
- MAAS: disambiguate use of environment uuid between state server
and environment configuration (LP: #1240423).
- local: provider fails to start due to missing setup of bootstrap
storage (LP: #1240709).
- local: local provider deploys fail due to inclusion of lxc package
within LXC containers (LP: #1247299).
- Azure: bootstrap fails due to old API version headers (LP: #1246320).
- client: os.rename does not work on Windows (LP: #1240927).
- simplestreams: cannot create simplestreams data for Ubuntu Trusty
(LP: #1241666).
- cloud-init: Embed full cloud-archive keyring in metadata to avoid
calls to keyserver.ubuntu.com which fail in egress restricted
data center environments (LP: #1243861).
- core: regression - relation name regex is to restrictive (LP: #1245004).
-- James Page <james.p...@ubuntu.com> Thu, 21 Nov 2013 10:30:39 +0000
** Changed in: juju-core (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1246556
Title:
lxc containers broken with maas
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1246556/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
