Actions
Bug #9858
closedWhen upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ran without errors."
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When we upgrade rudder-agent, the file /etc/cron.d/rudder-agent-uuid is created (see http://www.rudder-project.org/redmine/issues/3930 and http://www.rudder-project.org/redmine/issues/3925 )
This file now calls check_rudder_agent, and it became verbose in 4.0
So during upgrade, we create this cron file ( https://github.com/Normation/rudder-packages/blob/master/rudder-agent/SOURCES/rudder-agent-postinst ) without the > /dev/null, and the file is deleted afterward by techniques
We should probably:- in 4.0 redirect to > /dev/null in the cron
- remove this cron in version 4.1 (cause of the file was in 2.7.2 ...)
Actions