curtin

  1. Bug #1511589
  2. Comment #16

Comment 16 for bug 1511589

Revision history for this message
David Britton (dpb) wrote : Re: [Bug 1511589] Re: maas provider, hwclock out of sync means juju will not work

On Wed, Jun 22, 2016 at 11:18 AM, Mike Pontillo <<email address hidden>
> wrote:

> If we just want a ballpark, cloud-init already contacts MAAS via HTTP,
> and there is already a "Date:" header we could scrape. To what extent do
> we trust that? (Enough to always apply it on
> commissioning/enlistment/deployment, or just as a fallback if NTP isn't
> working?)
>
>
That reminds me Mike, enlistment and commissioning even use this date
header (I think) to adjust for any local skew, but only for using the oauth
token that it has been provided -- it's why enlisting/commissioning the
node works fine with a very old clock. What doesn't happen is the next
logical steps of setting the system clock and then the hwclock.

See: bug #978127

--
David Britton <email address hidden>