This bug was fixed in the package pollinate - 4.14-0ubuntu1
---------------
pollinate (4.14-0ubuntu1) xenial; urgency=medium
* pollinate, pollinate.1: LP: #1554152
- change the failure mode of pollinate, so as to more cleanly
tolerate network failures
- add a --strict option to re-enable the previous behavior,
ie, strictly exit non-zero if pollinate fails for any reason
- we've always promised that pollinate would operate on a best-effort
basis, improving the prng seeding when possible, but failing
gracefully when not possible; as such, we've made good on the first
half of that promise, however, the latter half has proven
troublesome; this is due to the fact that if pollinate exits
non-zero, then its callers (cloud-init, maas, etc.) may well
interpret the behavior strictly as a failure to boot the system,
when in fact that's not the case; instead, we'll clearly print
a warning to syslog, and we'll retry the seeding on next pollinate
service start (e.g. a reboot); moreover, we'll carry a --strict
flag in the case that users want to opt into the previous behavior
-- Dustin Kirkland <[email protected]> Tue, 13 Oct 2015 10:16:12
-0700
** Changed in: pollinate (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1554152
Title:
pollinate fails in many circumstances, cloud-init reports that
failure, maas reports node failed deployment
Status in cloud-init:
New
Status in MAAS:
New
Status in cloud-init package in Ubuntu:
New
Status in pollinate package in Ubuntu:
Fix Released
Bug description:
cloud-init runs pollinate via 'cc_seed_random.py' config job.
Some points
a.) in addition to seeding via pollinate seed_random will seed the random
device with data from the datasource if it is provided (azure and openstack
provide a random seed for this purpose)
b.) we really want seed_random to run before ssh , so that keys are generated
with good entropy in place.
c.) seed_random runs early via 'init_modules' mostly to accomplish 'b'.
Unfortunately, network is not guaranteed at this point if the datasource is a
'local' datasource (such as config drive).
e.) in many cases pollinate will not have access to
https://entropy.ubuntu.com (due to firewall or disconnected)
f.) in xenial, cloud-init reports events to maas as they occur, and when this
module fails, it reports that.
g.) maas marks nodes as failed deployment when cloud-init reports failure
End result, if you dont have access to entropy.ubuntu.com, then you
fail deployment.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cloud-init 0.7.7~bzr1176-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
NonfreeKernelModules: ufs qnx4 hfsplus hfs minix ntfs msdos
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Mon Mar 7 17:30:00 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1554152/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
