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.):

duplicate node name + "kubectl get nodes"

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

BUG REPORT

Kubernetes version (use kubectl version)

kubectl version

Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.4", GitCommit:"3b417cc4ccd1b8f38ff9ec96bb50a81ca0ea9d56", GitTreeState:"clean", BuildDate:"2016-10-21T02:48:38Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.4", GitCommit:"3b417cc4ccd1b8f38ff9ec96bb50a81ca0ea9d56", GitTreeState:"clean", BuildDate:"2016-10-21T02:42:39Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

kubeadm version

kubeadm version: version.Info{Major:"1", Minor:"5+", GitVersion:"v1.5.0-alpha.2.421+a6bea3d79b8bba", GitCommit:"a6bea3d79b8bbaa5e8b57482c9fff9265d402708", GitTreeState:"clean", BuildDate:"2016-11-03T06:54:50Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration:x86_64 desktop

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

Kernel (e.g. uname -a):Linux ubuntu-2 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Install tools:kubeadm

Others:

What happened:

We have two nodes, the master name was ubuntu-2 while the minion node was ubuntu-3.

kubectl get nodes

NAME STATUS AGE

ubunbu-3 Ready 10h

ubuntu-2 Ready 1d

If we add another node with same node name ubuntu-3, it just added without checking whether the node name had existed or not:

kubectl get nodes

NAME STATUS AGE

ubunbu-3 Ready 10h

ubuntu-2 Ready 1d

ubuntu-3 Ready 26m

What you expected to happen:

If we add node using 'kubeadm join' with node name already exists, we should return failed with error messages: "duplicate node name"

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

kubeadm join (node with name ubuntu-3, for example)

In master node 'kubectl get nodes'

NAME STATUS AGE

ubunbu-3 Ready 10h

ubuntu-2 Ready 1d

Add another node with name ubuntu-3

NAME STATUS AGE

ubunbu-3 Ready 10h <-----duplicate node name ubuntu-3

ubuntu-2 Ready 1d

ubuntu-3 Ready 26m <------duplicate node name ubuntu-3

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

KubeletNotReady container runtime is down

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.4", GitCommit:"dd6b458ef8dbf24aff55795baa68f83383c9b3a9", GitTreeState:"clean", BuildDate:"2016-08-01T16:45:16Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.4", GitCommit:"dd6b458ef8dbf24aff55795baa68f83383c9b3a9", GitTreeState:"clean", BuildDate:"2016-08-01T16:38:31Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}

Environment: What does that mean?

Cloud provider or hardware configuration: AWS

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

PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Kernel (e.g. uname -a):

Linux ip-172-20-1-41 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux

Install tools:

Others:

What happened: Nodes turn to NotReady with the following message on the describe output:

KubeletNotReady container runtime is down. WARNING: CPU hardcapping unsupported

This is the output of the sudo docker version command on the node:

Client:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:39 2016
OS/Arch: linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

The node does not seem to recover from this failure so I have to kill it and the auto scaling group brings up another one instead.

What you expected to happen: Nodes should remain in a Ready state or at least recover from such failures.

How to reproduce it (as minimally and precisely as possible): It just happens once in two days approximately.

Anything else do we need to know:

This is the daemon.log.txt from the time the node went down