You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NTP v4 requests fail on macOS runners, exclusively. Other runners (such as ubuntu) or local macOS work just fine.
Platforms affected
Azure DevOps
GitHub Actions - Standard Runners
GitHub Actions - Larger Runners
Runner images affected
Ubuntu 20.04
Ubuntu 22.04
Ubuntu 24.04
macOS 13
macOS 13 Arm64
macOS 14
macOS 14 Arm64
macOS 15
macOS 15 Arm64
Windows Server 2019
Windows Server 2022
Windows Server 2025
Image version and build link
I wasn't able to find the image version. Where's the Set up job section?
Is it regression?
No
Expected behavior
NTPv4 requests should come through.
Actual behavior
According to the tests in our codebase and debugging, the NTPv4 request payload is successfully sent but responses are never received, they time out.
Repro steps
I've created an issue to track the test in our codebase with which we had this issue. You can have a look at this issue for information on how to reproduce it: logos-co/nomos#1211
Manual CLI tests showed that the only request that works is to NTPv3 servers, specifically to time.windows.com. I tested that using the sntp command, that's the only one that returns a success. This same behaviour happens with our tests.
The text was updated successfully, but these errors were encountered:
Hi @strinnityk - We will start investigating on this issue and will update you accordingly. Can you please share the workflow run you have tried for this issue.
Description
NTP v4 requests fail on macOS runners, exclusively. Other runners (such as ubuntu) or local macOS work just fine.
Platforms affected
Runner images affected
Image version and build link
I wasn't able to find the image version. Where's the
Set up job
section?Is it regression?
No
Expected behavior
NTPv4 requests should come through.
Actual behavior
According to the tests in our codebase and debugging, the NTPv4 request payload is successfully sent but responses are never received, they time out.
Repro steps
I've created an issue to track the test in our codebase with which we had this issue. You can have a look at this issue for information on how to reproduce it: logos-co/nomos#1211
Manual CLI tests showed that the only request that works is to NTPv3 servers, specifically to
time.windows.com
. I tested that using thesntp
command, that's the only one that returns a success. This same behaviour happens with our tests.The text was updated successfully, but these errors were encountered: