Architecture #3930
closed
Rudder-agent cron file now use check-rudder-agent script (/opt/rudder/bin/check-rudder-agent)
Added by Nicolas PERRON about 11 years ago.
Updated about 11 years ago.
Category:
System techniques
Description
Since #3925 the rudder-agent cron file should use /opt/rudder/bin/check-rudder-agent instead of having the code directly in the cron file.
The bug #3925 concerned Rudder 2.4 so I guess this ticket should be in 2.4 too.
- Target version changed from 2.4.9 to 2.7.3
Nicolas PERRON wrote:
Since #3925 the rudder-agent cron file should use /opt/rudder/bin/check-rudder-agent instead of having the code directly in the cron file.
The bug #3925 concerned Rudder 2.4 so I guess this ticket should be in 2.4 too.
The rudder-agent cron file exists since 2.6, not 2.4. And it does not seems really necessary, it is more a feature than a bug so it seems logic to be included in 2.7
- Status changed from New to 14
- Project changed from 24 to Rudder
- Category set to System techniques
- Target version changed from 2.7.3 to 2.7.4
- Target version changed from 2.7.4 to 2.8.0~beta1
- Target version changed from 2.8.0~beta1 to 2.8.0~rc1
- Status changed from 14 to 12
- Assignee changed from Nicolas PERRON to Matthieu CERDA
- Subject changed from Since #3925 the rudder-agent cron file should be change to use check-rudder-agent script to Rudder-agent cron file now use check-rudder-agent script (/opt/rudder/bin/check-rudder-agent)
- Status changed from 12 to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~rc1, which was released on Friday 25/10/2013.
Check out:
- Related to Bug #9858: When upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ran without errors." added
Also available in: Atom
PDF