yahoo-eng-team team mailing list archive

[James Falcon <1511589@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2593

** Bug watch added: github.com/canonical/cloud-init/issues #2593
   https://github.com/canonical/cloud-init/issues/2593

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

-- 
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:
  Expired
Status in curtin:
  Triaged
Status in falkor:
  Fix Released
Status in juju-core:
  Invalid
Status in MAAS:
  Fix Released

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