Instalition error (Kubespray version - 2.24)

kubernetes-sigs / kubespray

Deploy a Production Ready Kubernetes Cluster

Apache License 2.0

15.83k stars 6.41k forks source link

Instalition error (Kubespray version - 2.24) #10859

Open thejvmshid opened 7 months ago

thejvmshid commented 7 months ago

What happened?

telegram-cloud-photo-size-2-5319149905144566249-y I gave this errir whern instalition kubespray

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

kundan2707 commented 7 months ago

@thejvmshid log is not visible clearly. Can you extract it in text document and upload it?

VannTen commented 7 months ago

/triage needs-information

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 3 months ago

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:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

kundan2707 commented 2 months ago

/remove-lifecycle rotten

kundan2707 commented 2 months ago

@thejvmshid you can close this issue if you havnt faced this issue again.