Systemd unit file broken if not running on master server in cluster #211
Description
Summary
We run our cb-event-forwarder on a separate server rather than our cluster master, this server is fully dedicated to the cb-event-forwarder and we subscribe to events via RabbitMQ.
In a recent update the following line was added to the cb-event-forwarder.service unit file:
ExecStartPre=/bin/bash -c /usr/share/cb/integrations/event-forwarder/cb-edr-fix-permissions.sh
This will fail on standalone cb-event-forwarder instances with the following error:
No cb user, please install CB EDR before running this script
Since this returns an exit code of 2 the systemd service will fail to startup. The fix for me was commenting out that ExecStartPre but I believe this script failing shouldn't make the whole systemd service fail, or it shouldn't be included in the systemd unit file.