Skip to content

test: mitigate clock drift in lima e2e fixture#350

Merged
jason-lynch merged 1 commit intomainfrom
test/mitigate-lima-clock-drift
Apr 17, 2026
Merged

test: mitigate clock drift in lima e2e fixture#350
jason-lynch merged 1 commit intomainfrom
test/mitigate-lima-clock-drift

Conversation

@jason-lynch
Copy link
Copy Markdown
Member

Summary

Lima has a known issue where the guest OS clock can drift on macOS. This causes issues with certificates, scheduled tasks, and other operations that depend on the system time.

This commit mitigates the issue by:

  • Altering the chronyd configuration to allow for large time jumps
  • Running chronyc -a makestep every time we deploy control plane

This fixes the clock drift every time you run one of these make targets:

make deploy-lima-fixture
make update-lima-fixture
make reset-lima-fixture

Testing

# update your fixture to get the chronyd config change
make deploy-lima-fixture

# verify the system clocks are accurate
ansible -i ./e2e/fixtures/outputs/lima.inventory.yaml all -m command -a 'date'

Lima has a known issue where the guest OS clock can drift on macOS. This
causes issues with certificates, scheduled tasks, and other operations
that depend on the system time.

This commit mitigates the issue by:

- Altering the chronyd configuration to allow for large time jumps
- Running `chronyc -a makestep` every time we deploy control plane

This fixes the clock drift every time you run one of these make targets:

```sh
make deploy-lima-fixture
make update-lima-fixture
make reset-lima-fixture
```
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 17, 2026

Warning

Rate limit exceeded

@jason-lynch has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 57 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 2 minutes and 57 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dff026af-1100-44e2-a411-6dea5e9cc0c2

📥 Commits

Reviewing files that changed from the base of the PR and between 3618ded and 1ef1c88.

📒 Files selected for processing (2)
  • e2e/fixtures/Makefile
  • e2e/fixtures/roles/install_prerequisites/tasks/main.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch test/mitigate-lima-clock-drift

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codacy-production
Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

TIP This summary will be updated as you push new changes. Give us feedback

@jason-lynch jason-lynch merged commit d102c5d into main Apr 17, 2026
3 checks passed
@jason-lynch jason-lynch deleted the test/mitigate-lima-clock-drift branch April 17, 2026 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants