-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachprod: Install and configure chrony on GCE clusters #62108
Conversation
I created a cluster using this change:
|
Fixes cockroachdb#62063 In cockroachdb#31577 we switched to `chrony` for AWS, but not for CGE. By default they GCE clusters based on Ubuntu 16.04 use `ntp`. This patch installs `chrony` (and automatically removes `ntp`) on GCE and configures `chrony` to use Google's time server. Release note: None
The optional CI failures don't look related, but I can rebase again, just in case. |
Potentially related: #62060 |
Sounds the same to me. Thank you! |
Interesting. We frequently see clock offset panics in our attempts at long-running roachtests such as #47652. I had poked at that in the past and never got anywhere, but maybe this will help. Either way thank you for looking into this! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought GCE VMs had good time synchronization out of the box that obviated the need for chrony. My knowledge is admittedly a few years out of date. I'm fine to see if this helps.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @rail)
bors r+ |
Build succeeded: |
Fixes #62063
In #31577 we switched to
chrony
for AWS, but not for CGE. By defaultthey GCE clusters based on Ubuntu 16.04 use
ntp
.This patch installs
chrony
(and automatically removesntp
) on GCEand configures
chrony
to use Google's time server.Release note: None