Skip to content

Fix time_server test's dead PUB5 NTP servers #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ddemlow merged 1 commit into from
Nov 2, 2026
Merged

Fix time_server test's dead PUB5 NTP servers #390

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions tests/integration/integration_config.yml.j2
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,10 +35,14 @@ sc_config:
# pool.ntp.org servers frequently return KOD.
# time.google.com does not complain.
source: time.google.com
# We need 2 NTP servers.
# Set them up per ci-infra/ntp-chrony/Readme.md.
time_server_a: 10.5.11.5
time_server_b: 10.5.11.75
# We need 2 NTP servers. 10.5.11.5/10.5.11.75 were dedicated chrony VMs on PUB5/XLab
# (see ci-infra/ntp-chrony/Readme.md), dead in the same 2026-10-27 outage as the rest of
# that network. Repointed 2026-11-02 at two public NTP providers instead of rebuilding
# that infra -- smtp-relay.gmail.com (used by the smtp test, same config file) already
# confirms these clusters have outbound internet reachability. Avoid pool.ntp.org
# domains for either value -- the comment above is still correct, they return KOD.
time_server_a: time.google.com
time_server_b: time.cloudflare.com
time_zone:
zone: US/Eastern
dns_config:
Expand Down
Loading