Restart receptor if reload config fails

[TheRealHaoLiu]

RUNNING HANDLER [ansible.receptor.setup : Reload Receptor] ****************************************************************************
fatal: [remote-execution]: FAILED! => {"changed": true, "cmd": ["receptorctl", "--socket", "/var/run/receptor/receptor.sock", "reload"], "delta": "0:00:00.174893", "end": "2023-10-23 20:36:19.259809", "failed_when_result": true, "msg": "non-zero return code", "rc": 3, "start": "2023-10-23 20:36:19.084916", "stderr": "ERROR: a non-reloadable config action 'work-command' was modified or added. Must restart receptor for these changes to take effect ERRORCODE 3", "stderr_lines": ["ERROR: a non-reloadable config action 'work-command' was modified or added. Must restart receptor for these changes to take effect ERRORCODE 3"], "stdout": "", "stdout_lines": []}
...ignoring

this happen when u install receptor as a execution node on a VM that was previously a hop node

[Zokormazo]

Question here. Let say the same run changed receptor systemd override file in /etc/ , do we launch daemon-reload somehow before this reload in that case, or do we need to include the daemon_reload field in this systemd call?

[rebeccahhh]

Do you need to