Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

No.

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

I searched for the words "Tim Hockin" on my chat roster. :-)

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

FEATURE.

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.4", GitCommit:"3eed1e3be6848b877ff80a93da3785d9034d0a4f", GitTreeState:"clean"}

Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.5", GitCommit:"25eb53b54e08877d3789455964b3e97bdd3f3bce", GitTreeState:"clean"}

Environment:

Cloud provider or hardware configuration: GCE/GKE

OS (e.g. from /etc/os-release): VERSION="14.04.5 LTS, Trusty Tahr"

Kernel (e.g. uname -a): Linux edpin-linux.mtv.corp.google.com 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Install tools:

Others:

What happened:

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.

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:

Events:

FirstSeen LastSeen Count From SubobjectPath Type Reason Message

6m 6m 1 {default-scheduler } Normal Scheduled Successfully assigned dirserver-3381994805-8cfe6 to gke-cluster-1-default-pool-bb87ddba-hogl

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.

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.

What you expected to happen:

A message such as:

"Can't connect to PD in a different zone: requested PD in "zones/us-central1-a", pod is running in "zones/us-central1-c".

or somesuch.

How to reproduce it (as minimally and precisely as possible):

gcloud compute disks create --size=100GB some-name --zone=us-central1-a

Then configure your yaml job to run on us-central1-c.

Anything else do we need to know:

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you found any duplicates, you should instead reply there or use the 👍 icon in the upper-right of the issue message):

lookup on 8.8.8.8:53: no such host

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version):

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"}

Environment:

Cloud provider or hardware configuration: 3 GB RAM, 60 GB hard disk

OS (e.g. from /etc/os-release): Ubuntu 14.04.1 LTS

Kernel (e.g. uname -a): 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

Install tools:

Others:

What happened:

I ran a single node cluster version using hack/local-up-cluster.sh and tried running petset examples provided - both galera and redis. The peer-finder keeps complaining with the following error : lookup <service> on 8.8.8.8:53: no such host where service is either redis or galera.

What you expected to happen:

Expect the petset to start properly.

How to reproduce it (as minimally and precisely as possible):

Run a single node cluster using hack/local-up-cluster.sh and run the petset example.

Anything else do we need to know: