This message was deleted.

It will always show failed when you stop it. Low priority bug that it doesn't exit with 0 when you signal it to shutdown

Thanks @creamy-pencil-82913 that's good to know 🙂 Any tips on stopping etcd? Do I just stop it with crictl or should I enter the container and issue etdctl something?

If you just shut down the node normally, systemd will go through the normal process of signalling things

Ok thanks @creamy-pencil-82913 🙂 Yeah I've looked into using that but as you're saying it's a little brutal.

Right now we intentionally leave things running when the main rke2 process is stopped. If this is causing problems in your environment, feel free to open an issue. Making it wait and stop all the control-plane components before exiting would be non-trivial but I could see the reason for wanting it.

Yeah I've read a few GH issues regarding stopping rke2-server and I get your points. For me it's not an issue but logically, if the rke2-server unit starts something, it should also shut it down.