Hello. After creating and provisioning a downstream cluster via Rancher, is there a reason why stopping the service on the OS is not adhering to a zero exit code?

~$ systemctl stop rke2-agent
...

Stopping Rancher Kubernetes Engine v2 (agent)...
time="2025-03-13T07:19:45+02:00" level=warning msg="signal received: \"terminated\", canceling context..."
time="2025-03-13T07:19:45+02:00" level=fatal msg="context canceled"
rke2-agent.service: Main process exited, code=exited, status=1/FAILURE
rke2-agent.service: Failed with result 'exit-code'.
rke2-agent.service: Unit process 153962 (containerd-shim) remains running after unit stopped.
rke2-agent.service: Unit process 155172 (containerd-shim) remains running after unit stopped.
rke2-agent.service: Unit process 1570202 (containerd-shim) remains running after unit stopped.
Stopped Rancher Kubernetes Engine v2 (agent).
rke2-agent.service: Consumed 10h 38min 57.713s CPU time.

I have done a cordon and drain beforehand; not sure what the expected behavior should be.