rke2 server process shows up as rke2 agent in process list

[brandond]

Environmental Info:
RKE2 Version:

rke2 version v1.28.11+rke2r1 (6b12d7a783238b72da8450fa1b6ec587cebb79ed)
go version go1.21.11 X:boringcrypto

Node(s) CPU architecture, OS, and Version:
n/a

Cluster Configuration:
n/a

Describe the bug:

Server process shows up as agent in ps output:

root@rke2-server-1:/# kubectl get node -o wide
NAME            STATUS   ROLES                       AGE   VERSION           INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION   CONTAINER-RUNTIME
rke2-server-1   Ready    control-plane,etcd,master   38s   v1.28.11+rke2r1   172.17.0.8    <none>        Ubuntu 22.04.4 LTS   6.6.0-1001-aws   containerd://1.7.17-k3s1

root@rke2-server-1:/# ps auxfww | grep bin/rke2
root        5835  0.0  0.0   3472  1792 pts/1    S+   00:09   0:00  \_ grep --color=auto bin/rke2
root           1  0.0  1.7 1334528 74752 pts/0   Ssl+ 00:07   0:00 /usr/local/bin/rke2 agent

Steps To Reproduce:

• Install RKE2
• Start server systemd unit: systemctl start rke2-server
• Check ps output; note that it reports the process title as rke2 agent

Expected behavior:
Process shows as server

Actual behavior:
Process shows as agent

Additional context / logs:

This appears to have been introduced in v1.28.11+rke2r1, this same behavior is not seen in v1.28.10+rke2r1
I do not see this on the same month's v1.30.2+rke2r1, but I do see it on v1.29.6+rke2r1 and v1.27.15+rke2r1 which suggests that the root is somewhere in a backport PR on the K3s side.

[brandond]

Found the root cause.

I backported k3s-io/k3s@48ff3bc but failed to also backport the fix from k3s-io/k3s@bf6e874

This is due to a missing backport commit, so only affects 1.29, 1.28, and 1.27

[brandond]

Closing this master issue, as it only exists on release branches < 1.30