oxidecomputer / oxidecomputer/omicron
boundary NTP zones came online without any sources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In a recent dogfood update the two boundary NTP services came online with no sources configured in chrony. This update had a prolonged period of time where connectivity was not available in the beginning.
Once connectivity was available, I issued a chronyc -n online in each NTP zone. I noticed that the boundary zones were never configured with an upstream source address. This was observed via chronyc -n sources being empty. I eventually restarted the sled agent on each boundary sled, which caused the NTP zones to get deleted and recreated. When they came back online, they had a source configuration, contacted the upstream NTP servers, and shortly after, all the sleds were time-synchronized.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how boundary NTP zones are created and how their chrony sources are configured, then reproduce the reported sequence with connectivity unavailable at startup. Use chronyc -n online and chronyc -n sources to inspect the zones; done means an upstream source is configured after connectivity returns and the sleds become time-synchronized without restarting the sled agent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100