-
Notifications
You must be signed in to change notification settings - Fork 353
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
k0s stop fails on OpenRC #4212
Comments
The issue is marked as stale since no activity has been recorded in 30 days |
The issue is marked as stale since no activity has been recorded in 30 days |
I can reproduce this in the inttests as well: $ make check-singlenode K0S_KEEP_AFTER_TESTS=always
[ ... ]
--- PASS: TestSingleNodeSuite (75.33s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp (71.71s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify (12.26s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/kineIsDefaultStorage (0.05s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/noControllerJoinTokens (0.09s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/noWorkerJoinTokens (0.09s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/leader_election_disabled_for_scheduler (0.00s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/leader_election_disabled_for_controller_manager (0.00s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/killK0s (5.21s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/etcdIsRunning (0.01s)
--- PASS: TestSingleNodeSuite/TestK0sGetsUp/verify/no_kube-bridge_address_in_default_config (0.09s)
PASS
ok github.com/k0sproject/k0s/inttest/singlenode 75.351s
$ docker exec -ti TestSingleNodeSuite-controller0 k0s reset
FATA[2024-05-29 15:17:01] k0s seems to be running! please stop k0s before reset.
$ docker exec -ti TestSingleNodeSuite-controller0 k0s stop
Error: exit status 1 |
Seems like there are no
But there is a |
Yes, I fooled myself with the inttest, as it's not using OpenRC at all 😏 Anyhow, I initially encountered it on a VM that was using OpenRC. I think the main task here is to incorporate the parts of kardanios service which are used by k0s and fix the error messages. It'll be much easier to sort out any real issues then. |
Before creating an issue, make sure you've checked the following:
Platform
Version
v1.29.2+k0s.0
Sysinfo
`k0s sysinfo`
What happened?
On OpenRC,
sudo k0s stop
fails withError: exit status 1
.Steps to reproduce
Expected behavior
It works ¯\(ツ)/¯
Actual behavior
Needs to be stopped manually.
Screenshots and logs
No response
Additional context
There's some log statement in the
k0s reset
output which probably shouldn't be there, as well.The text was updated successfully, but these errors were encountered: