Comment 15 for bug 1257082

So I just ran face first into this bug. Unless I'm missing something,
I don't think ntp being installed by default helps at all. MAAS and
Juju (for the MAAS provisioner) both depend on servers having an
accurate clock early in the boot process; ntpdate achieves this
because it's willing to jump time; ntp is not (for valid reasons).

And, even if I'm wrong about that, we still need a fix for trusty and
precise. Could we not just fix/reverse the logic in ntpdate-debian so
that it prefers dhcp provided NTP servers if one is found? Or at the
very least have it fallback to dhcp provided NTP if it can't find an
ntp.conf?