Description of problem:

When you hard-reboot a foremanctl-deployed system, the foreman service will fail to come up again because the old server.pid is still on-disk

How reproducible:

100%

Is this issue a regression from an earlier version:

regression compared to non-foremanctl systems

Steps to Reproduce:

1. deploy machine

2. reboot the VM via power-cycle or similar

3.

Actual behavior:

foreman.service fails to start with:

quadlet.example.com foreman[1921]: A server is already running. Check /usr/share/foreman/tmp/pids/server.pid.

Expected behavior:
service starts up, even after an unclean shutdown

Business Impact / Additional info: