This bug was fixed in the package cloud-init - 0.7.7~bzr1182-0ubuntu1
---------------
cloud-init (0.7.7~bzr1182-0ubuntu1) xenial; urgency=medium
* New upstream snapshot.
* systemd changes enforcing intended ordering (cloud-init-local.service
before networking and cloud-init.service before it comes up).
* when reading dmidecode data, return found but unset value as "" rather
than failing to decode that value.
* add default user to 'lxd' group and create groups when necessary
(LP: #1539317)
* No longer run pollinate in seed_random (LP: #1554152)
* Enable BigStep data source.
-- Scott Moser <smo...@ubuntu.com> Mon, 14 Mar 2016 09:58:56 -0400
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554152
Title:
pollinate fails in many circumstances, cloud-init reports that
failure, maas reports node failed deployment
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
