© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
well, this will probably mess things up, but i'll attempt to explain a few things.
The summary is that I'm almost certain this does not affect your maas enlistment or commissioning.
a.) maas images in 'released' are old.
this is quite unfortunate, but the images there are out of date and need updating. We're looking into ways we can produce up to date images without risk of regression to users.
since this is old, 'pollinate' inside is old. And since it uses its own certificate, that fails to work. Any unpatched ubuntu image will show that error. It is "just" a warning though.
This is why updating to daily got rid of the red-herring problem for you.
b.) cloud-init really has nothing to do with pollinate. It calls it is all. MAAS can instruct it *not* to call pollinate, but that may defeat the purpose that pollinate is serving. Note, seed is sometimes believed to be more useful in VMs which have less entropy, and maas is targetting hardware. So, in the case where maas is pointed at "real hardware", disabling pollinate may be less harmful. (note, i'm not speaking as a qualified security engineer here).
c.) we should probably add to maas metadata service some random seed. This would alleviate 'b' as then we *would* be getting a random seed from somewhere.
d.) I've submitted merge proposal to document random_seed better at https:/