-
-
Notifications
You must be signed in to change notification settings - Fork 1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hanging at TASK [k3s_agent : Manage k3s service] #466
Comments
I was able to get 4/5 nodes working after "Delete nodes and do a reinstall, re-clone branch and setup fresh". A possible culprit might have been resizing the partition on the nodes, or installing net-tools package. Checking the log output the following lines appear right after:
Let me know if I should attach the full log, in case that is helpful! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Not able to install the playbook
Expected Behavior
Installation to be successful
Current Behavior
It should not hang at:
and instead, it should tell me what the issue is at the very least.
The log output where it hangs give the following output:
Steps to Reproduce
ansible-playbook ./site.yml -i ./inventory/my-cluster/hosts.ini -bK
ansible-playbook ./reset.yml -i ./inventory/my-cluster/hosts.ini
ansible-playbook ./reboot.yml -i ./inventory/my-cluster/hosts.ini
ansible-playbook ./site.yml -i ./inventory/my-cluster/hosts.ini -bK
, same error occursContext (variables)
Running playbook from:
Operating system: Ventura 13.5.1 (22G90)
Hardware: Macbook Pro M2 Max
Deploying in:
Operating system: Proxmox cloud-based Ubuntu VM clones 22.04 amd64 (Jammy)
Hardware: 4 Core, 4 GB RAM, 64 GB NVMe Drive.
Variables Used
all.yml
Possible Solution
The text was updated successfully, but these errors were encountered: