The master branch reported an error during the initial installation.

[ZhangChengJi]

What happened?

The master branch reported an error during the initial installation. This error suggests that kubeadm init failed due to some pre-flight checks not passing. Let's break down the errors: However, I had not installed anything before, and the environment was completely clean.

"start": "2025-02-19 16:04:09.336860",
"stderr": "error execution phase preflight: [preflight] Some fatal errors occurred:\n\t[ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists\n\t[ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists\n\t[ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists\n\t[ERROR Port-10250]: Port 10250 is in use\n[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...\nTo see the stack trace of this error execute with --v=5 or higher",
"stderr_lines": [
"error execution phase preflight: [preflight] Some fatal errors occurred:",
"\t[ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists",
"\t[ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists",
"\t[ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists",
"\t[ERROR Port-10250]: Port 10250 is in use",
"[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...",
"To see the stack trace of this error execute with --v=5 or higher"
],
"stdout": "[init] Using Kubernetes version: v1.32.0\n[preflight] Running pre-flight checks",
"stdout_lines": [
"[init] Using Kubernetes version: v1.32.0",
"[preflight] Running pre-flight checks"
]
}

What did you expect to happen?

Resolve this issue

How can we reproduce it (as minimally and precisely as possible)?

I use Crio and Cilium.

OS

NAME="Rocky Linux"
VERSION="9.4 (Blue Onyx)"

Version of Ansible

ansible [core 2.16.14]

Version of Python

3.12.1

Version of Kubespray (commit)

master

Network plugin used

cilium

Full inventory with variables

[kube_control_plane]
k8s-1 ansible_host=192.168.1.131 ansible_user=root # ip=10.3.0.1 etcd_member_name=etcd1

[etcd:children]
kube_control_plane

[kube_node]
k8s-1 ansible_host=192.168.1.131 ansible_user=root
k8s-2 ansible_host=192.168.1.132 ansible_user=root

Command used to invoke ansible

ansible-playbook -i inventory/mycluster/inventory.ini cluster.yml -b -vvv

Output of ansible run

https://gist.github.com/ZhangChengJi/9515ce19cedcd85c134a30b45b2dbd2b

Anything else we need to know

No response

[vdveldet]

Port 10250 is in use indicates the the port is used by a service, so kubeadm stops.