This message was deleted.
# k3s
a
This message was deleted.
p
Can somebody please help me with this issue ?
b
I have no idea what would make Ubuntu fail to remove a network.
You tried the normal things like rebooting the node?
My best guess is that there's some socket file/lock that halting it from progressing and the reinstall fixes it?
But you're trying to intentionally force a reboot/shutdown and figure out how to bring it back up?
c
you corrupted your filesystem when you pulled the plug on it without shutting it down cleanly
so you have a bunch of empty or corrupt state files, as well as corrupt binaries
p
@bland-article-62755 no it was hard reboot. For example use case you have power off and then on while cluster is steering up again power off happened
So I tried also microk8s and it I was not able to break doing the same. They use dqlite instead of SQLite. So could db be corrupted ?
b
I think @creamy-pencil-82913 is on the right track with this.
If you shutdown a node ungracefully, (pulling the power, or even just shutdown from the cli while it isn't fully established yet) the OS/filesystem isn't equipped to handle that kind of distruption.
Unless you're using something that's stateless/container based for your OS like FedoraCore OS or Suse Transactional server, elemental, etc..
The ungraceful bit is means more than just hard hard reboot. Hard reboots should still be graceful. It's possible to recover from a loss of power event, but not guaranteed with just normal Ubuntu.