-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
K3s does not start after restoration #9305
Comments
Please follow the directions given in the docs. You created a new cluster with your Step 1, then stopped it, and did not clean up with the |
Hello @dereknola @brandond i have tried and followed the steps you mentioned and I am still getting the same error |
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 45 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions. |
Environmental Info:
K3s Version:
v1.28.5+k3s1
Node(s) CPU architecture, OS, and Version:
Linux etcd-test 6.2.0-1018-azure #18~22.04.1-Ubuntu SMP Tue Nov 21 19:25:02 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
3 servers 2 agents
Describe the bug:
From my cluster of 3 servers 2 agents the backup snapshots are saved in Wasabi bucket. I have used one of these backup and tried to restore the cluster on a new azure vm.
i have performed the following steps on my new vm:
bash systemctl stop k3s
Copied the backup file to the new vm. Restoring the cluster using the following command
Output of the above command:
Expected behavior:
Expecting to see the cluster up and running
Actual behavior:
K3s doesnt start.
When i restart my k3s i get the following error
The text was updated successfully, but these errors were encountered: