This bug was fixed in the package cloud-init - 0.7.0~bzr659-0ubuntu1
---------------
cloud-init (0.7.0~bzr659-0ubuntu1) quantal; urgency=low
* New upstream snapshot.
* add signal handlers to more cleanly exit
* add logging fallback in case logging fails
* documentation fix for landscape config (LP: #1042764)
* do not write a comment in /etc/hostname (LP: #1052664)
* fix incorrect ubuntu mirrors for 'ports' arches [Robbie Basak]
* fix generation of hostname based on ip address in datasource
(LP: #1050962) [Andy Grimm]
* remove 'start networking' from cloud-init-nonet and replace it
with container specific fixes (LP: #1031065)
* fix landscape configuration so client will run (LP: #1042758)
* enable all available datasources (adding AltCloud and None)
* fix bug where user data scripts re-ran on upgrade from 10.04 versions
(LP: #1049146)
-- Scott Moser <smo...@ubuntu.com> Wed, 19 Sep 2012 22:08:51 -0400
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1031065
Title:
cloud-init-nonet runs 'start networking' explicitly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+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
