646563 - all buildbot masters must run ntp correctly, puppet changes required

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Amy Rich [:arr] [:arich]]

In order to implement time checking on the buildbot masters, each master must be running ntp with the correct configuration.  There are two puppet configuration changes that should be made to facilitate this:

1) modify the dhclient configuration on each buildbot server to not add NTP configuration information to /etc/ntp.conf by adding the line:

PEERNTP=no

2) put /etc/ntp.conf under puppet control with the following content:

####  This file under configuration management control
####  DO NOT EDIT MANUALLY

restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery
restrict 127.0.0.1 
restrict -6 ::1
driftfile /var/lib/ntp/drift
keys /etc/ntp/keys
server ntp.build.mozilla.org

Comment 1

[Chris AtLee [:catlee]]

I don't know that this host is working:

[root@buildbot-master4 build_master5]# ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 10.12.75.12     .INIT.          16 u    - 1024    0    0.000    0.000   0.000

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

It looks like it's still initializing - the hosts talk to each other for a while before actually syncing.

Comment 3

[Amy Rich [:arr] [:arich]]

I also added:

restrict 10.0.0.0 mask 255.0.0.0

to ntp.conf to allow the 10 subnet.

Comment 4

[Chris AtLee [:catlee]]

ntp.conf updated on production-master{01,02,03}, buildbot-master{1,2,3,5}

Comment 5

[Chris AtLee [:catlee]]

buildbot-master{4,6} will be updated via puppet once I've got that committed and deployed

Comment 6

[Chris AtLee [:catlee]]

done enough for now. puppet manifests got reverted, but that's a different bug.