title: Flink HA JobManager cluster cannot elect a leader
body: <p>I'm trying to deploy Apache Flink 1.6 on kubernetes. With following the tutorial at <a href="https://ci.apache.org/projects/flink/flink-docs-release-1.6/ops/jobmanager_high_availability.html" rel="nofollow noreferrer">job manager high availabilty</a>
  page. I already have a working Zookeeper 3.10 cluster from its logs I can see that it's healthy and doesn't configured to Kerberos or SASL.All ACL rules are let's every client to write and read znodes. When I start the cluster everything works as expected every JobManager and TaskManager pods are successfully getting into Running state and I can see the connected TaskManager instances from the master JobManager's web-ui. But when I delete the master JobManager's pod, the other JobManager pod's cannot elect a leader with following error message on any JobManager-UI in the cluster.</p>
  
  <pre><code>{
    "errors": [
      "Service temporarily unavailable due to an ongoing leader election. Please refresh."
    ]
  }
  </code></pre>
  
  <p>Even if I restart this page nothing changes. It stucks at this error message.
  My suspicion is, the problem is related with <code>high-availability.storageDir</code> option. I already have a working (tested with <a href="https://github.com/rusher81572/cloudExplorer" rel="nofollow noreferrer">CloudExplorer</a>)  <a href="https://www.minio.io/" rel="nofollow noreferrer">minio</a> s3 deployment to my k8s cluster. But flink <strong>cannot</strong> write anything to the s3 server. Here you can find every config from <a href="https://gist.github.com/rfum/6891bb390ce031da9e3086a27d1499a5" rel="nofollow noreferrer">github-gist</a>.</p>