This message was deleted.

Why is it failing to find the config files?

yes.. /etc/rancher is created as separate partition. carbon-sadc-dev-devtools-v1-np2-w1c3-m-vdw9g-qg5d2 ~]# df -h | grep rancher /dev/mapper/appvg-etcrancherlv 2.9G 92K 2.8G 1% /etc/rancher /dev/mapper/appvg-rancherlv 196G 17G 170G 9% /var/lib/rancher

sounds like you don’t have your mount priorities set up properly in systemd, and services are starting without that partition mounted

True, /etc/rancher is very light weighted. Considering my past edge cases with OS/App filesystem combinations created filesystem crashes in RKE1, hence separated OS filesystems and rancher. Is this causing the issue, should i move away from separated file system for /etc/rancher as well? [carbon-sadc-dev-devtools-v1-np2-w1c3-m-vdw9g-qg5d2 ~]# df -h | grep rancher /dev/mapper/appvg-etcrancherlv 2.9G 92K 2.8G 1% /etc/rancher /dev/mapper/appvg-rancherlv 196G 17G 170G 9% /var/lib/rancher [root@carbon-sadc-dev-devtools-v1-np2-w1c3-m-vdw9g-qg5d2 ~]# cd /etc/rancher/ [carbon-sadc-dev-devtools-v1-np2-w1c3-m-vdw9g-qg5d2 rancher]# ls -ltr total 32 drwx------. 2 root root 16384 Apr 21 2025 lost+found drwxr-xr-x. 2 root root 4096 Jan 15 2026 node drwxr-xr-x. 5 root root 4096 Jan 15 2026 rke2 drwx------. 2 root root 4096 Apr 15 16:30 agent [carbon-sadc-dev-devtools-v1-np2-w1c3-m-vdw9g-qg5d2 rancher]# du -shx * 16K agent 16K lost+found 8.0K node 52K rke2 [root@carbon-sadc-dev-devtools-v1-np2-w1c3-m-vdw9g-qg5d2 rancher]# cat /etc/fstab /dev/mapper/systemvg-rootlv / ext4 defaults 1 1 UUID=14a21bec-4711-449b-a10d-ca8396380169 /boot ext4 defaults 1 2 /dev/mapper/systemvg-homelv /home ext4 defaults,nodev,nosuid, 0 0 /dev/mapper/systemvg-optlv /opt ext4 defaults 1 2 /dev/mapper/systemvg-tmplv /tmp ext4 defaults,nodev,noexec,nosuid 0 0 /dev/mapper/systemvg-usrlv /usr ext4 defaults 1 2 /dev/mapper/systemvg-usrlocallv /usr/local ext4 defaults 1 2 /dev/mapper/systemvg-varlv /var ext4 defaults,nodev,nosuid, 0 0 /dev/mapper/systemvg-cachednflv /var/cache/dnf ext4 defaults 1 2 /dev/mapper/systemvg-varloglv /var/log ext4 defaults,nodev,noexec,nosuid 0 0 /dev/mapper/systemvg-auditlv /var/log/audit ext4 defaults,noexec,nodev,nosuid 0 0 /dev/toolsvg/splunklv /usr/splunk ext4 defaults 0 0 /dev/toolsvg/taniumlv /opt/Tanium ext4 defaults 0 0 /dev/toolsvg/rapid7lv /opt/rapid7 ext4 defaults,nodev 0 0 /dev/toolsvg/crowdstrikelv /opt/CrowdStrike ext4 defaults,nodev 0 0 tmpfs /dev/shm tmpfs defaults,nodev,noexec,nosuid 0 0 /dev/appvg/containerdlv /var/lib/containerd ext4 defaults 0 0 /dev/appvg/kubeletlv /var/lib/kubelet ext4 defaults 0 0 /dev/mapper/appvg-logkuberneteslv /var/log/kubernetes ext4 defaults 0 0 /dev/mapper/appvg-optrke2lv /opt/rke2 ext4 defaults 0 0 /dev/mapper/appvg-etckuberneteslv /etc/kubernetes ext4 defaults 0 0 /dev/mapper/appvg-etcrancherlv /etc/rancher ext4 defaults 0 0 /dev/toolsvg/fluentlv /opt/fluent ext4 defaults,nodev 0 0 /dev/mapper/appvg-rancherlv /var/lib/rancher ext4 nodev,defaults 1 2

If you are not capable of ensuring it gets mounted reliably, don't do it

thanks for suggestions