This is really problematic. New nodes do not come with synchronized clocks.
And client nodes may not be on a public facing network interface (at least not at boot time).
What about changing the configuration of the MAAS master to automatically run a time service
and have the client nodes set their clocks from it (+1 for #2)?
Failing that, allow the tickets or whatever timestamped credential is being passed to be valid
for +/-24 hours? I like this less than having the clock set accurately at boot, since if you got a
batch of 100+ nodes with ill-set clocks, it would be *way* to much manual labor to set in in the bios.
This bug nearly had me willing to walk away from MAAS as DOA.
This is really problematic. New nodes do not come with synchronized clocks.
And client nodes may not be on a public facing network interface (at least not at boot time).
What about changing the configuration of the MAAS master to automatically run a time service
and have the client nodes set their clocks from it (+1 for #2)?
Failing that, allow the tickets or whatever timestamped credential is being passed to be valid
for +/-24 hours? I like this less than having the clock set accurately at boot, since if you got a
batch of 100+ nodes with ill-set clocks, it would be *way* to much manual labor to set in in the bios.
This bug nearly had me willing to walk away from MAAS as DOA.