yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

The way that I'd like to have this fixed in MAAS is 
 a.) for maas to add vendor-data into the meta-data service
 b.) cloud-init to add support for configuring ntp
 c.) maas to declare in vendor-data what the ntp service is

The reason I've suggested this in vendor-data is that this is a maas
setting, which would be relevant to all environments (commissioning,
enlistment and user-deployed).  The user-deployed environment has the
*users* provided user-data, but maas would still be able to provide
vendor-data there.


** Also affects: cloud-init
   Importance: Undecided
       Status: New

** Changed in: cloud-init
       Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

-- 
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/1511589

Title:
  maas provider, hwclock out of sync means juju will not work

Status in cloud-init:
  Confirmed
Status in curtin:
  Triaged
Status in falkor:
  Fix Released
Status in juju-core:
  Invalid
Status in MAAS:
  Incomplete

Bug description:
  MAAS provides no means to ensure the hardware clock is set, and juju
  relies on accurate clocks.

  Leading to errors like this when you bootstrap on machines that
  otherwise works fine:

  "ERROR juju.cmd supercommand.go:430 gomaasapi: got error back from server:
  401 OK (Authorization Error: \'Expired timestamp: given 1446087606 and now
  1446094822 has a greater difference than threshold 300\')\nERROR failed to
  bootstrap environment: subprocess encountered error code 1\n\')'), 1),
  (u'waiting', 179), (u'succeeded', 10)]"

  The only thing a user can do is touch each machine, sometimes booting
  them into an OS to fix their hwclock (which can still drift from that
  point, of course).

  This error path is exposed when the stock 'ntpdate' from ubuntu does
  not work, for instance, if your lab is behind a proxy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1511589/+subscriptions