[Bug 978127] Re: incorrect time on node causes failed oauth

[Scott Moser]

There are 2 pieces to this fix, both of which are fixed in 12.10.
a.) cloud-init portion.  This fix is in the latest set of precise "released" ephemeral images.  They include cloud-init from 12.10.  It accounts for 401 or 403 return.
b.) "maas-signal" portion.  maas-signal is used during commissioning, and it reports commissioning results back.  maas-signal is part of maas (/etc/maas/commissioning-user-data).  This was fixed in revision 1242 [1].

The behavior that I would expect in 12.04 with broken hardware clocks at
this point is for enlistment to work, commissioning to get user-data,
but then to failto report home as done.  I think for 12.04 I would
recommend the modification of the ephemeral image to include the running
of 'ntp-date' as described in comment 5.

--
[1] http://bazaar.launchpad.net/~maas-maintainers/maas/trunk/revision/1242

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/978127

Title:
  incorrect time on node causes failed oauth

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