Skip to content

NTP v4 requests fail on macOS #11939

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.

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

Open
3 of 15 tasks
strinnityk opened this issue Apr 3, 2025 · 2 comments
Open
3 of 15 tasks

NTP v4 requests fail on macOS #11939

strinnityk opened this issue Apr 3, 2025 · 2 comments

Comments

@strinnityk
Copy link

Description

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.

@ijunaidm1
Copy link
Contributor

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.

@ijunaidm1 ijunaidm1 self-assigned this Apr 3, 2025
@susmitamane
Copy link
Contributor

susmitamane commented Apr 14, 2025

Hi @strinnityk, we're still looking into this issue, but the reproducing steps provided so far aren't entirely clear. Could you please help us by sharing the following details:

  • A link to the last successful run
  • A link to the most recent failed run
  • Detailed steps to reproduce the issue, including the mandatory example project code and workflow (if the project is private)

Without complete reproduce steps, it’s difficult for us to isolate and resolve the problem.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants