TASK [kubernetes/master : kubeadm | Initialize first master] **********************************************************************
Friday 20 March 2020 17:44:10 +0800 (0:00:00.440) 0:57:46.769 **********
skipping: [master1]
FAILED - RETRYING: kubeadm | Initialize first master (3 retries left).

FAILED - RETRYING: kubeadm | Initialize first master (2 retries left).
FAILED - RETRYING: kubeadm | Initialize first master (1 retries left).
fatal: [master]: FAILED! => {
“attempts”: 3,
“changed”: true,
“cmd”: [
“timeout”,
“-k”,
“300s”,
“300s”,
“/usr/local/bin/kubeadm”,
“init”,
“–config=/etc/kubernetes/kubeadm-config.yaml”,
“–ignore-preflight-errors=all”,
“–skip-phases=addon/coredns”,
“–upload-certs”
],
“delta”: “0:05:00.129084”,
“end”: “2020-03-20 18:04:35.793620″,
“failed_when_result”: true,
“rc”: 124,
“start”: “2020-03-20 17:59:35.664536″
}

STDOUT:

[init] Using Kubernetes version: v1.17.3
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using ‘kubeadm config images pull’
[kubelet-start] Writing kubelet environment file with flags to file “/var/lib/kubelet/kubeadm-flags.env”
[kubelet-start] Writing kubelet configuration to file “/var/lib/kubelet/config.yaml”
[kubelet-start] Starting the kubelet
[certs] Using certificateDir folder “/etc/kubernetes/ssl”
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] External etcd mode: Skipping etcd/ca certificate authority generation
[certs] External etcd mode: Skipping etcd/server certificate generation
[certs] External etcd mode: Skipping etcd/peer certificate generation
[certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation
[certs] External etcd mode: Skipping apiserver-etcd-client certificate generation
[certs] Using the existing “sa” key
[kubeconfig] Using kubeconfig folder “/etc/kubernetes”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/admin.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/kubelet.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/controller-manager.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/scheduler.conf”
[control-plane] Using manifest folder “/etc/kubernetes/manifests”
[control-plane] Creating static Pod manifest for “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[control-plane] Creating static Pod manifest for “kube-controller-manager”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[control-plane] Creating static Pod manifest for “kube-scheduler”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory “/etc/kubernetes/manifests”. This can take up to 5m0s
[kubelet-check] Initial timeout of 40s passed.

STDERR:

W0320 17:59:36.646109 33048 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0320 17:59:36.646238 33048 validation.go:28] Cannot validate kubelet config - no validator is available
[WARNING Port-6443]: Port 6443 is in use
[WARNING Port-10259]: Port 10259 is in use
[WARNING Port-10257]: Port 10257 is in use
[WARNING FileAvailable–etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
[WARNING FileAvailable–etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
[WARNING FileAvailable–etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
[WARNING IsDockerSystemdCheck]: detected “cgroupfs” as the Docker cgroup driver. The recommended driver is “systemd”. Please follow the guide at https://kubernetes.io/docs/setup/cri/
[WARNING Port-10250]: Port 10250 is in use
W0320 18:00:08.294173 33048 images.go:98] WARNING: DEPRECATED use of the “hyperkube” image for the Kubernetes control plane. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:31.597827 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-apiserver”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:31.598329 33048 manifests.go:214] the default kube-apiserver authorization-mode is “Node,RBAC”; using “Node,RBAC”
W0320 18:00:31.860007 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-controller-manager”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:31.863386 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-scheduler”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:32.056888 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-apiserver”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:32.056972 33048 manifests.go:214] the default kube-apiserver authorization-mode is “Node,RBAC”; using “Node,RBAC”
W0320 18:00:32.057179 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-controller-manager”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:32.057668 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-scheduler”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:32.059337 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-apiserver”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:32.059376 33048 manifests.go:214] the default kube-apiserver authorization-mode is “Node,RBAC”; using “Node,RBAC”
W0320 18:00:32.059441 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-controller-manager”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.
W0320 18:00:32.059802 33048 images.go:39] WARNING: DEPRECATED use of the “hyperkube” image in place of “kube-scheduler”. The “useHyperKubeImage” field will be removed from future kubeadm config versions and possibly ignored in future releases.

MSG:

non-zero return code

NO MORE HOSTS LEFT ****************************************************************************************************************

PLAY RECAP ************************************************************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=0

master : ok=435 changed=91 unreachable=0 failed=1

master1 : ok=421 changed=88 unreachable=0 failed=0

node1 : ok=411 changed=84 unreachable=0 failed=0

node2 : ok=312 changed=69 unreachable=0 failed=0

node3 : ok=312 changed=69 unreachable=0 failed=0