yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This is fixed in cloud-init 0.7.7

** Changed in: cloud-init
       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:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in pollinate package in Ubuntu:
  Fix Released
Status in pollinate source package in Trusty:
  Fix Committed

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