Issue when I try to add new worker node with scale.yml #11020
Labels
kind/bug
Categorizes issue or PR as related to a bug.
triage/duplicate
Indicates an issue is a duplicate of other open issue.
What happened?
Hi,
I try to add a new node in our on-premises cluster.
Following the documentation:
I guess I missed something, could you help me to solve this issue
Regards
Jean
What did you expect to happen?
New Worker node added to the cluster
How can we reproduce it (as minimally and precisely as possible)?
Add a new worker node with the following command on a running cluster :
ansible-playbook -i inventory/icluster/hosts.yaml --become --become-user=root -e kube_version=v1.28.7 --limit=iworker6 scale.yml
The cluster has access to internet and all worker are in the same network (all ports open)
OS
Ansible host
Linux 5.15.0-97-generic x86_64
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
Worker
Linux 5.15.0-100-generic x86_64
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
Version of Ansible
Version of Python
Python 3.10.12
Version of Kubespray (commit)
a1cf829
Network plugin used
calico
Full inventory with variables
inventory.txt
Command used to invoke ansible
ansible-playbook -i inventory/icluster/hosts.yaml --become --become-user=root -e kube_version=v1.28.7 --limit=iworker6 scale.yml
Output of ansible run
ansible_los_18_03.txt
Anything else we need to know
No response
The text was updated successfully, but these errors were encountered: