Comment 7 for bug 1257082

Robie: Yes, changing NTPDATE_USE_NTP_CONF=no makes everything work, at least when I change it after the node is deployed. I am not aware of how to try this with a preeseed late_command. Do you have instructions for me to attempt this? Will this mean all newly-deployed MAAS nodes get this change?

Below is the output from one of the nodes testing NTP_CONF on and off. It shows the script working correctly and using the NTP servers from DHCP when set to =no.
---------------------------------------------
root@sled204n2:~# grep ^NTPDATE_USE_NTP_CONF= /etc/default/ntpdate
NTPDATE_USE_NTP_CONF=yes
root@sled204n2:~# ntpdate-debian
20 Jan 21:37:02 ntpdate[14019]: no server suitable for synchronization found
root@sled204n2:~# date
Thu Jan 20 21:37:05 UTC 2000
root@sled204n2:~# nano /etc/default/ntpdate
root@sled204n2:~# grep ^NTPDATE_USE_NTP_CONF= /etc/default/ntpdate
NTPDATE_USE_NTP_CONF=no
root@sled204n2:~# ntpdate-debian
 3 Dec 19:27:26 ntpdate[14027]: step time server 172.31.23.1 offset 437694593.235280 sec
root@sled204n2:~# date
Tue Dec 3 19:27:31 UTC 2013
root@sled204n2:~#