Skip to content
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

Could not find the requested service kubelet: host #136

Closed
laszlof opened this issue Jan 12, 2023 · 2 comments
Closed

Could not find the requested service kubelet: host #136

laszlof opened this issue Jan 12, 2023 · 2 comments
Labels

Comments

@laszlof
Copy link

laszlof commented Jan 12, 2023

Receiving the above error message when attempting to use this playbook. It looks like its not doing a systemd daemon-reload after installing kubelet.

Full error output here:

TASK [geerlingguy.kubernetes : Ensure kubelet is started and enabled at boot.] ******************************************************************************************
fatal: [kube-node01]: FAILED! => {"changed": false, "msg": "Could not find the requested service kubelet: host"}
fatal: [kube-master]: FAILED! => {"changed": false, "msg": "Could not find the requested service kubelet: host"}
fatal: [kube-node02]: FAILED! => {"changed": false, "msg": "Could not find the requested service kubelet: host"}
fatal: [kube-node03]: FAILED! => {"changed": false, "msg": "Could not find the requested service kubelet: host"}

This is on CentOS 7.9.2009 on the host system, installing the latest kubernetes + docker.

If I run systemctl daemon-reload and rerun the playbook, it makes it past this task.

@stale
Copy link

stale bot commented May 21, 2023

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@stale stale bot added the stale label May 21, 2023
@github-actions
Copy link

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant