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

Apply failed on Alpine Linux #698

Open
Malaccoda opened this issue May 4, 2024 · 2 comments
Open

Apply failed on Alpine Linux #698

Malaccoda opened this issue May 4, 2024 · 2 comments

Comments

@Malaccoda
Copy link

Malaccoda commented May 4, 2024

INFO[0002] * Running clean-up for phase: Acquire exclusive host lock
...
DEBU[0002] [ssh] 10.0.0.6:22: stopped lock cycle, removing file
...
DEBU[0002] [ssh] 10.0.0.6:22: executing `rm -f -- /run/lock/k0sctl 2> /dev/null`
INFO[0002] ==> Apply failed
FATA[0003] apply failed - log file saved to /root/.cache/k0sctl/k0sctl.log: failed on 5 hosts:
...
 - [ssh] 10.0.0.6:22: command failed: client exec: ssh session wait: Process exited with status 1

I tried it with enabling cgroups like mentionned in the other thread but didnt change anything.
Alpine Version 3.19.1

@twz123
Copy link
Member

twz123 commented May 6, 2024

@Malaccoda are you able to share the k0sctl log file, so we can see what k0sctl was up to before the apply failed?

Without more context, my initial guess would be that there's no unique machine ID on the hosts. On Alpine, you can enable those via rc-update add machine-id boot && /etc/init.d/machine-id start (as root).

Moreover, can you share the output of k0s sysinfo from one of the failing hosts?

@kke
Copy link
Contributor

kke commented May 14, 2024

The log snippet is unrelated, there's something that happened before that caused this. The lock file management logging has been toned down a bit in #713.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants