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.
There are 2 pieces to this fix, both of which are fixed in 12.10. commissioning- user-data) . This was fixed in revision 1242 [1].
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/
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.
-- bazaar. launchpad. net/~maas- maintainers/ maas/trunk/ revision/ 1242
[1] http://