Actions
Bug #3803
closedrudder-agent init script ignores the /opt/rudder/etc/disable-agent flag file
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If you run "service rudder-agent restart", it will launch the CFEngine daemons, even if the /opt/rudder/etc/disable-agent is present.
This isn't very serious, since as soon as the agent runs, it will kill these daemons and halt. But still, it's wasteful, and confusing. For example, if a sysadmin doesn't know about the /opt/rudder/etc/disable-agent flag, and tries to restart rudder-agent, he may well be confused - the init script says OK, it started everything, but a few minutes later rudder-agent is not working still.
We should adapt the init script to detect this file and complain loudly about it.
Actions