all buildbot masters must run ntp correctly, puppet changes required

RESOLVED FIXED

Status

P2
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: arich, Assigned: catlee)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
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
(Assignee)

Comment 1

8 years ago
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
It looks like it's still initializing - the hosts talk to each other for a while before actually syncing.
(Reporter)

Comment 3

8 years ago
I also added:

restrict 10.0.0.0 mask 255.0.0.0

to ntp.conf to allow the 10 subnet.
(Assignee)

Comment 4

8 years ago
ntp.conf updated on production-master{01,02,03}, buildbot-master{1,2,3,5}
(Assignee)

Comment 5

8 years ago
buildbot-master{4,6} will be updated via puppet once I've got that committed and deployed
(Reporter)

Updated

8 years ago
Group: mozilla-corporation-confidential
(Assignee)

Updated

8 years ago
Depends on: 607179
Priority: -- → P2
(Assignee)

Comment 6

8 years ago
done enough for now. puppet manifests got reverted, but that's a different bug.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.