Repository navigation
Fix time_server test's dead PUB5 NTP servers - #390
Merged
Merged
Conversation
time_server_a/b (10.5.11.5/10.5.11.75) were dedicated chrony VMs on PUB5/XLab's network (see ci-infra/ntp-chrony/Readme.md), dead in the same 2026-10-27 outage as the rest of that network. HyperCore validates NTP server reachability server-side, so the test failed with "X is not a valid NTP server" rather than just storing an unreachable value. Repointed at two public NTP providers (time.google.com, time.cloudflare.com) instead of rebuilding dedicated chrony infra on Indy-lab -- smtp-relay.gmail.com (used by the smtp test, same config file) already confirms these clusters have outbound internet reachability. Avoided pool.ntp.org domains for both values, per this file's own existing comment that they return KOD. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
`time_server_a`/`time_server_b` (`10.5.11.5`/`10.5.11.75`) were two dedicated chrony NTP VMs on PUB5/XLab's network (see `ci-infra/ntp-chrony/Readme.md`), dead in the same 2026-10-27 outage as the rest of that network. HyperCore validates NTP server reachability server-side, so the test fails outright with `"X is not a valid NTP server"` rather than just storing an unreachable value.
Repointed at two public NTP providers (`time.google.com`, `time.cloudflare.com`) instead of rebuilding dedicated chrony infra on Indy-lab — `smtp-relay.gmail.com` (used by the `smtp` test, same config file) already confirms these clusters have outbound internet reachability. Avoided `pool.ntp.org` domains for either value, per this file's own existing comment that they return KOD (rate-limiting rejection).
Test plan
🤖 Generated with Claude Code