-
Notifications
You must be signed in to change notification settings - Fork 803
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
Some file are not created (k3s.service.env, k3s-agent.service.env) #368
Comments
K3s-ansible is not responsible for creating the |
First the errors were censored, when setting System is a freshly installed Debian 11/bullseye server, ansible collection is from the master branch here. |
I probably have a similar issue. Perhaps it has something to do with this change bc03d1c This file is not created So probably as @jkrenzer offered, we should add
|
I'm still unable to reproduce this issue, I can clearly find the k3s-agent.service.env on a fresh installed ubuntu node:
Both agent and server service and service.env files are created when the k3s install script runs on the nodes.
The creation line is linked above |
What does your inventory.yaml look like, are you changing any of the k3s configuration? |
Ah I think I found the problem. On debian 11, the install script is not getting downloaded correctly
|
Hi!
Due to the missing parameter
create: true
in theansible.builtin.lineinfile
command, some files are not created when they are empty and thus an installation from a clean system fails.So far I identified following steps:
In roles/k3s_server/tasks/main.yaml:
In roles/k3s_agent/tasks/main.yaml:
Cheers,
Jörn
The text was updated successfully, but these errors were encountered: