This bug was fixed in the package cloud-init - 0.6.3~bzr539-0ubuntu1 --------------- cloud-init (0.6.3~bzr539-0ubuntu1) precise; urgency=low
* New upstream snapshot. * add ability to configure Acquire::http::Pipeline-Depth via cloud-config setting 'apt_pipelining' (LP: #942061) * if cloud-config settings removed default certificats (remove-defaults), then seed package ca-certificates to not install new ones on upgrade. * run-parts now uses internal implementation rather than separate command. * add MaaS datasource (LP: #942061) * debian/cloud-init.postinst: address population of apt_pipeline setting on installation. * debian/cloud-init.postinst: support configuring cloud-init maas datasource via preseed values cloud-init/maas-metadata-url and cloud-init/maas-credentials. (LP: #942061) * debian/cloud-init.postinst: support for (LP: #924375) -- Scott Moser <smo...@ubuntu.com> Fri, 09 Mar 2012 16:37:01 -0500 ** Branch linked: lp:ubuntu/cloud-init ** 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/942061 Title: need support for maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/942061/+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