Add back check_time

BACKENDS.md

@@ -18,6 +18,7 @@ These backend classes allow backend-specific configuration of the cluster.
   - [Troubleshooting](#troubleshooting)
     - [Cleaning Up and Fixing "Out of Space" Errors](#cleaning-up-and-fixing-out-of-space-errors)
     - [macOS File Sharing](#macos-file-sharing)
+    - [Clock sync errors](#clock-sync-errors)
 - [Using existing nodes](#using-existing-nodes)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
@@ -70,6 +71,12 @@ Docker for Mac must be configured to allow `/private` to be bind mounted into Do
 This is the default.
 See Docker > Preferences > File Sharing.
 
+#### Clock sync errors
+
+On various platforms, the clock can get out of sync between the host machine and Docker containers.
+This is particularly problematic if using `check_time: true` in the DC/OS configuration.
+To work around this, run `docker run --rm --privileged alpine hwclock -s`.
+
 ## Using existing nodes
 
 It is possible to use existing nodes on any platform with DC/OS E2E.

spelling_private_dict.txt

@@ -1,3 +1,4 @@
+adam
 admin
 args
 aufs
@@ -14,6 +15,7 @@ dict
 dir
 env
 genconf
+hwclock
 init
 ip
 mesos

src/dcos_e2e/backends/_docker/__init__.py

@@ -484,6 +484,13 @@ def ip_list(nodes: Set[Node]) -> List[str]:
         config = {
             'agent_list': ip_list(nodes=self.agents),
             'bootstrap_url': 'file://' + str(self._bootstrap_tmp_path),
+            # Without this, we see errors like:
+            # "Time is not synchronized / marked as bad by the kernel.".
+            # Adam saw this on Docker for Mac 17.09.0-ce-mac35.
+            #
+            # In that case this was fixable with:
+            #   $ docker run --rm --privileged alpine hwclock -s
+            'check_time': 'false',
             'cluster_name': 'DCOS',
             'exhibitor_storage_backend': 'static',
             'master_discovery': 'static',