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.

Sign up for GitHub

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

Jump to bottom

pkill in roles/reset/tasks/main.yml assumes the path for the k3s data directory ends with "k3s" #161

Closed
jon-stumpf opened this issue Dec 14, 2021 · 1 comment
Closed

pkill in roles/reset/tasks/main.yml assumes the path for the k3s data directory ends with "k3s" #161

jon-stumpf opened this issue Dec 14, 2021 · 1 comment

Comments

@jon-stumpf
Copy link
Contributor

jon-stumpf commented Dec 14, 2021 •
edited
Loading

k3s_server_location was introduced in #133 and can be used to change the location of the data directory (default: /var/lib/rancher/k3s). In roles/reset/tasks/main.yml, pkill is used to kill k3s processes with a pattern that begins with "k3s/data". "k3s" is part of what can change with k3s_server_location.

If one changes the location and the path does not end with "k3s", the containerd-shim processes will not be killed.
jon-stumpf added a commit to jon-stumpf/k3s-ansible that referenced this issue Dec 14, 2021
@jon-stumpf
FIX k3s-io#161: Updated pkill to use k3s_server_location in roles/res…
b3e2df8 
…et/tasks/main.yml

Signed-off-by: Jon S. Stumpf <[email protected]>
@jon-stumpf jon-stumpf mentioned this issue Dec 15, 2021
Closed
@dereknola
Copy link
Member

Resolved with #230

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jon-stumpf @dereknola