title: Kops rolling-update fails with "Cluster did not pass validation" for master node
body: <p>For some reason my master node can no longer connect to my cluster after upgrading from kubernetes 1.11.9 to 1.12.9 via kops (version 1.13.0). In the manifest I'm upgrading <code>kubernetesVersion</code> from 1.11.9 -> 1.12.9. This is the only change I'm making. However when I run <code>kops rolling-update cluster --yes</code> I get the following error:</p>
  
  <pre><code>Cluster did not pass validation, will try again in "30s" until duration "5m0s" expires: machine "i-01234567" has not yet joined cluster.
  Cluster did not validate within 5m0s
  </code></pre>
  
  <p>After that if I run a <code>kubectl get nodes</code> I no longer see that master node in my cluster.</p>
  
  <p>Doing a little bit of debugging by sshing into the disconnected master node instance I found the following error in my api-server log by running <code>sudo cat /var/log/kube-apiserver.log</code>:</p>
  
  <p><code>controller.go:135] Unable to perform initial IP allocation check: unable to refresh the service IP block: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp 127.0.0.1:4001: connect: connection refused</code></p>
  
  <p>I suspect the issue might be related to etcd, because when I run <code>sudo netstat -nap | grep LISTEN | grep etcd</code> there is no output.</p>
  
  <p>Anyone have any idea how I can get my master node back in the cluster or have advice on things to try?</p>