<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):</p>
<p dir="auto">No.</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):</p>
<p dir="auto">I searched for the words "Tim Hockin" on my chat roster. :-)</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):</p>
<p dir="auto">FEATURE.</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<p dir="auto">Client Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.4", GitCommit:"3eed1e3be6848b877ff80a93da3785d9034d0a4f", GitTreeState:"clean"}<br>
Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.5", GitCommit:"25eb53b54e08877d3789455964b3e97bdd3f3bce", GitTreeState:"clean"}</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: GCE/GKE</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): VERSION="14.04.5 LTS, Trusty Tahr"</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): Linux edpin-linux.mtv.corp.google.com 3.13.0-91-generic <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35930943" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/138" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kubernetes/pull/138/hovercard" href="https://github.com/kubernetes/kubernetes/pull/138">#138</a>-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:</p>
<p dir="auto">I tried to attach a PD in the wrong zone. I had pods in us-central1-c but this operator copy-and-pasted some examples around and created the PD in us-central1-a.</p>
<p dir="auto">Then the pod would not tell me why it was in ContainerCreating for long minutes. kubectl logs  didn't show anything useful and kubectl describe pod showed me this unhelpful message:</p>
<p dir="auto">Events:<br>
FirstSeen LastSeen    Count   From                            SubobjectPath   Type        Reason      Message</p>
<hr>
<p dir="auto">6m        6m      1   {default-scheduler }                            Normal      Scheduled   Successfully assigned dirserver-3381994805-8cfe6 to gke-cluster-1-default-pool-bb87ddba-hogl<br>
5m        23s     6   {kubelet gke-cluster-1-default-pool-bb87ddba-hogl}          Warning     FailedMount Unable to mount volumes for pod "dirserver-3381994805-8cfe6_default(fe8e0537-68c1-11e6-8f90-42010af00083)": Could not attach GCE PD "dirserver-logs". Timeout waiting for mount paths to be created.<br>
5m        23s     6   {kubelet gke-cluster-1-default-pool-bb87ddba-hogl}          Warning     FailedSync  Error syncing pod, skipping: Could not attach GCE PD "dirserver-logs". Timeout waiting for mount paths to be created.</p>
<p dir="auto"><strong>What you expected to happen</strong>:</p>
<p dir="auto">A message such as:<br>
"Can't connect to PD in a different zone: requested PD in "zones/us-central1-a", pod is running in "zones/us-central1-c".</p>
<p dir="auto">or somesuch.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<p dir="auto">gcloud compute disks create --size=100GB some-name --zone=us-central1-a</p>
<p dir="auto">Then configure your yaml job to run on us-central1-c.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.): No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you found any duplicates, you should instead reply there or use the 👍 icon in the upper-right of the issue message):</p>
<h2 dir="auto"><code class="notranslate">lookup on 8.8.8.8:53: no such host</code></h2>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one): BUG REPORT</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;3+&quot;, GitVersion:&quot;v1.3.0-alpha.0.6480+b7e87917462559-dirty&quot;, GitCommit:&quot;b7e879174625599c8c232f9d7e9bed9b7e7a9998&quot;, GitTreeState:&quot;dirty&quot;, BuildDate:&quot;2016-08-10T17:02:20Z&quot;, GoVersion:&quot;go1.6&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;3+&quot;, GitVersion:&quot;v1.3.0-alpha.0.6480+b7e87917462559-dirty&quot;, GitCommit:&quot;b7e879174625599c8c232f9d7e9bed9b7e7a9998&quot;, GitTreeState:&quot;dirty&quot;, BuildDate:&quot;2016-08-10T17:02:20Z&quot;, GoVersion:&quot;go1.6&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
"><pre class="notranslate"><code class="notranslate">Client Version: version.Info{Major:"1", Minor:"3+", GitVersion:"v1.3.0-alpha.0.6480+b7e87917462559-dirty", GitCommit:"b7e879174625599c8c232f9d7e9bed9b7e7a9998", GitTreeState:"dirty", BuildDate:"2016-08-10T17:02:20Z", GoVersion:"go1.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"3+", GitVersion:"v1.3.0-alpha.0.6480+b7e87917462559-dirty", GitCommit:"b7e879174625599c8c232f9d7e9bed9b7e7a9998", GitTreeState:"dirty", BuildDate:"2016-08-10T17:02:20Z", GoVersion:"go1.6", Compiler:"gc", Platform:"linux/amd64"}

</code></pre></div>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: 3 GB RAM, 60 GB hard disk</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): <code class="notranslate">Ubuntu 14.04.1 LTS</code></li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): <code class="notranslate">Linux vagrant 3.13.0-83-generic #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux</code></li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
I ran a single node cluster version using hack/local-up-cluster.sh and tried running petset examples provided - both galera and redis. The <code class="notranslate">peer-finder</code> keeps complaining with the following error : <code class="notranslate">lookup &lt;service&gt; on 8.8.8.8:53: no such host</code> where service is either <code class="notranslate">redis</code> or <code class="notranslate">galera</code>.</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
Expect the petset to start properly.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
Run a single node cluster using hack/local-up-cluster.sh and run the petset example.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>