This bug was fixed in the package juju-core - 1.17.6-0ubuntu1
---------------
juju-core (1.17.6-0ubuntu1) trusty; urgency=medium
* New upstream point release, including fixes for:
- br0 not bought up by cloud-init with MAAS provider (LP: #1271144).
- ppc64el enablement for juju/lxc (LP: #1273769).
- juju userdata should not restart networking (LP: #1248283).
- error detecting hardware characteristics (LP: #1276909).
- juju instances not including the default security group (LP: #1129720).
- juju bootstrap does not honor https_proxy (LP: #1240260).
* d/control,rules: Drop BD on bash-completion, install bash-completion
direct from upstream source code.
* d/rules: Set HOME prior to generating man pages.
* d/control: Drop alternative dependency on mongodb-server; juju now only
works on trusty with juju-mongodb.
-- James Page <james.p...@ubuntu.com> Mon, 24 Mar 2014 16:05:44 +0000
** Changed in: juju-core (Ubuntu Trusty)
Status: Triaged => 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/1248283
Title:
juju userdata should not restart networking
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1248283/+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
