-
Notifications
You must be signed in to change notification settings - Fork 715
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
Tests fail to start running due to ntp setup failure #339
Comments
Actually, if these commands are run beforehand then the tests start running as expected. |
That's a weird one. I don't know if this is a docker thing, but it looooks like whatever went wrong was some sort of issue with ntpdate: I mean, ntpdate isn't going to do anything anyway, because you can't change clocks in docker containers, right? Either way, this is an odd one. You say it's working now? |
It works only when Otherwise,
Err... given that, does that mean skew clock tests don’t work with the Docker setup? |
That is really strange! I'm not sure why ntpdate would say "no server suitable" when run by Jepsen, but be fine running it by SSH, and then be fine when Jepsen runs it afterwards.
Yeah, I assume so. It might be different on your platform, but at least on Debian's LXC, clocks aren't namespaced and can't be updated in containers. |
I'm trying to set up Jepsen testing in Dgraph's TeamCity CI infrastructure. The tests run OK when I spin up a new CI agent machine (Ubuntu machines on Google Cloud), SSH into the box and run tests in an interactive shell. i.e., after setting up the Jepsen cluster via ./up.sh I can run tests with this command.
But when this gets run via a triggered CI build, they always fail with NTP clock synchronization issues.
The text was updated successfully, but these errors were encountered: