Open thejvmshid opened 7 months ago
@thejvmshid log is not visible clearly. Can you extract it in text document and upload it?
/triage needs-information
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
@thejvmshid you can close this issue if you havnt faced this issue again.
What happened?
What did you expect to happen?
Instalition of Kubernetes
How can we reproduce it (as minimally and precisely as possible)?
ansible-playbook -i inventory/mvp/inventory.ini --become --become-user=root cluster.yml
OS
Ubuntu 22.04.3 LTS
Version of Ansible
Core 2.12.5
Version of Python
3.10.12
Version of Kubespray (commit)
origin/release-2.24
Network plugin used
calico
Full inventory with variables
No response
Command used to invoke ansible
No response
Output of ansible run
No response
Anything else we need to know
No response