Issue 1:
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:127

Aug 16 08:11:16.645: Couldn't delete ns "e2e-tests-v1job-gmj3l": namespace e2e-tests-v1job-gmj3l was not deleted within limit: timed out waiting for the condition, pods remaining: []

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:265

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 have found any duplicates, you should instead reply there.):

kubeadm arm

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

Bug

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.3",
GitCommit:"4957b090e9a4f6a68b4a40375408fdc74a212260", GitTreeState:"clean",
BuildDate:"2016-10-16T06:36:33Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"linux/arm"}

Environment:

Raspberry Pi 3

Cloud provider or hardware configuration:

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

HypriotOS v 1.0

Kernel (e.g. uname -a):

Linux m10 4.4.15-hypriotos-v7+ #1 SMP PREEMPT Mon Jul 25 08:46:52 UTC 2016 armv7l GNU/Linux

Install tools:

Others:

What happened:

Following kubeadm installation docs. I've installed the prereqs and proceeded with the init as follows:

kubeadm init --use-kubernetes-version v1.4.1 --pod-network-cidr=10.244.0.0/16

The command is stuck on:

master/pki> created keys and certificates in "/etc/kubernetes/pki"
<util/kubeconfig> created "/etc/kubernetes/kubelet.conf"
<util/kubeconfig> created "/etc/kubernetes/admin.conf"
<master/apiclient> created API client configuration
<master/apiclient> created API client, waiting for the control plane to become ready

Looking at docker on this node expecting to see images being installed for etcd, api-server, etc..

but docker images reports nothing. Guessing kubeadm is somehow no able to connect with local docker daemon? or the default Hypriot docker configuration is not jiving with kubeadm??

What you expected to happen:

kubeadm init to complete successfully

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

o Download Hypriot v1.0 image and flash on SD card

o Boot rp with SD card

o curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -

o cat < /etc/apt/sources.list.d/kubernetes.list

deb http://apt.kubernetes.io/ kubernetes-xenial main

EOF

o apt-get update

o apt-get install -y kubelet kubeadm kubectl kubernetes-cni

o kubeadm init --use-kubernetes-version v1.4.1 --pod-network-cidr=10.244.0.0/16

Anything else do we need to know:

Looking at /etc/kubernetes/manifests shows:

etcd.json kube-apiserver.json kube-controller-manager.json kube-scheduler.json

Inspecting journalctl on kubelet shows:

Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.467776 2787 kubelet_node_status.go:203] Setting node annotation to enable volume controller attach/detach
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.469033 2787 interface.go:248] Default route transits interface "eth0"
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.470261 2787 interface.go:93] Interface eth0 is up
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.471170 2787 interface.go:138] Interface "eth0" has 2 addresses :[192.168.0.92/24 fe80::ba27:ebff:fe24:986f/64].
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.471484 2787 interface.go:105] Checking addr 192.168.0.92/24.
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.471664 2787 interface.go:114] IP found 192.168.0.92
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.471831 2787 interface.go:144] valid IPv4 address for interface "eth0" found as 192.168.0.92.
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.471960 2787 interface.go:254] Choosing IP 192.168.0.92
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.497415 2787 kubelet_node_status.go:354] Recording NodeHasSufficientDisk event message for node m10
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.497616 2787 kubelet_node_status.go:354] Recording NodeHasSufficientMemory event message for node m10
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.497905 2787 kubelet_node_status.go:354] Recording NodeHasNoDiskPressure event message for node m10
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.498077 2787 kubelet_node_status.go:73] Attempting to register node m10
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.498243 2787 server.go:608] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"m10", UID:"m10", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'NodeHasSufficientDisk' Node m10 status is now: NodeHasSufficientDisk
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.498554 2787 server.go:608] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"m10", UID:"m10", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'NodeHasSufficientMemory' Node m10 status is now: NodeHasSufficientMemory
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.498823 2787 server.go:608] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"m10", UID:"m10", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'NodeHasNoDiskPressure' Node m10 status is now: NodeHasNoDiskPressure
Oct 26 17:19:31 m10 kubelet[2787]: E1026 17:19:31.501189 2787 kubelet_node_status.go:97] Unable to register node "m10" with API server: Post https://192.168.0.92:443/api/v1/nodes: dial tcp 192.168.0.92:443: getsockopt: connection refused
Oct 26 17:19:31 m10 kubelet[2787]: I1026 17:19:31.527656 2787 reflector.go:249] Listing and watching *api.Pod from pkg/kubelet/config/apiserver.go:43
Oct 26 17:19:31 m10 kubelet[2787]: E1026 17:19:31.531088 2787 reflector.go:203] pkg/kubelet/config/apiserver.go:43: Failed to list *api.Pod: Get https://192.168.0.92:443/api/v1/pods?fieldSelector=spec.nodeName%3Dm10&resourceVersion=0: dial tcp 192.168.0.92:443: getsockopt: connection refused
Oct 26 17:19:32 m10 kubelet[2787]: I1026 17:19:32.416745 2787 reflector.go:249] Listing and watching *api.Service from pkg/kubelet/kubelet.go:384
Oct 26 17:19:32 m10 kubelet[2787]: E1026 17:19:32.418995 2787 reflector.go:203] pkg/kubelet/kubelet.go:384: Failed to list *api.Service: Get https://192.168.0.92:443/api/v1/services?resourceVersion=0: dial tcp 192.168.0.92:443: getsockopt: connection refused
Oct 26 17:19:32 m10 kubelet[2787]: I1026 17:19:32.455119 2787 reflector.go:249] Listing and watching *api.Node from pkg/kubelet/kubelet.go:403
Oct 26 17:19:32 m10 kubelet[2787]: E1026 17:19:32.457560 2787 reflector.go:203] pkg/kubelet/kubelet.go:403: Failed to list *api.Node: Get https://192.168.0.92:443/api/v1/nodes?fieldSelector=metadata.name%3Dm10&resourceVersion=0: dial tcp 192.168.0.92:443: getsockopt: connection refused
Oct 26 17:19:32 m10 kubelet[2787]: I1026 17:19:32.531641 2787 reflector.go:249] Listing and watching *api.Pod from pkg/kubelet/config/apiserver.go:43
Oct 26 17:19:32 m10 kubelet[2787]: E1026 17:19:32.534040 2787 reflector.go:203] pkg/kubelet/config/apiserver.go:43: Failed to list *api.Pod: Get https://192.168.0.92:443/api/v1/pods?fieldSelector=spec.nodeName%3Dm10&resourceVersion=0: dial tcp 192.168.0.92:443: getsockopt: connection refused
Oct 26 17:19:33 m10 kubelet[2787]: I1026 17:19:33.419424 2787 reflector.go:249] Listing and watching *api.Service from pkg/kubelet/kubelet.go:384
Oct 26 17:19:33 m10 kubelet[2787]: E1026 17:19:33.421922 2787 reflector.go:203] pkg/kubelet/kubelet.go:384: Failed to list *api.Service: Get https://192.168.0.92:443/api/v1/services?resourceVersion=0: dial tcp 192.168.0.92:443: getsockopt: connection refused