This bug was fixed in the package pollinate - 4.18-0ubuntu1~16.04
---------------
pollinate (4.18-0ubuntu1~16.04) xenial-proposed; urgency=medium
* debian/pollinate.service:
- move to later in boot, after network starts, but before ssh starts
pollinate (4.17-0ubuntu1) yakkety; urgency=medium
* debian/pollinate.service:
- use the right flag file for LP: #1578833
pollinate (4.16-0ubuntu1) yakkety; urgency=medium
[ Martin Pitt ]
* Don't run pollinate.service in containers (as containers can't and should
not write the host's random pool) and when we already have a saved random
seeds (i. e. only on first boot). (LP: #1578833)
* Bump Standards-Version to 3.9.8 (no changes needed).
[ Dustin Kirkland ]
* pollinate: use timeout(1) to limit curl, related to LP: #1578833
-- Dustin Kirkland <[email protected]> Fri, 06 May 2016 11:36:02
-0500
** Changed in: pollinate (Ubuntu Xenial)
Status: Fix Committed => 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/1578833
Title:
pollinate should not run in containers and only for first boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1578833/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
