rancher: RKE2 Server & Agent Service Does not Start After Reboot on SLES 15.3
Issue details here: https://github.com/rancher/rke2/issues/3001
This only occurs with RKE2 clusters on SLES/Leap 15.3 & 15.4 provisioned via Rancher. In short, a Rancher-provisioned RKE2 cluster is not placing the rke2-server or agent service in /etc/systemd/system - provisioning is dropping them into /usr/local/lib instead.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 15 (4 by maintainers)
@Martin-Weiss Well, you have to ask internally for that. Iām just an end-user š
I can confirm it works with Rancher v2.6.9 and v1.24.9-rc4+rke2r1. RKE2 is installed in
/opt/rke2and unit files are located in/etc/systemd/systemfor rke2 agent and server and rancher-system-agent. So all looks good.