Project

General

Profile

Bug #9858

When upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ran without errors."

Added by Nicolas CHARLES 12 months ago. Updated 10 months ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

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 ...)

Related issues

Related to Rudder - Architecture #3930: Rudder-agent cron file now use check-rudder-agent script (/opt/rudder/bin/check-rudder-agent) Released 2013-09-17
Related to Rudder - Bug #7911: Add an output to all Rudder commands Released 2016-05-20

Associated revisions

Revision 5169f539
Added by Benoît PECCATTE 12 months ago

Fixes #9858: When upgrading Rudder, we get mails from cron saying \"ok: Rudder agent check ran without errors.\"

History

#1 Updated by Nicolas CHARLES 12 months ago

  • Related to Architecture #3930: Rudder-agent cron file now use check-rudder-agent script (/opt/rudder/bin/check-rudder-agent) added

#2 Updated by Nicolas CHARLES 12 months ago

#3 Updated by Nicolas CHARLES 12 months ago

#4 Updated by Nicolas CHARLES 12 months ago

  • Related to Bug #7911: Add an output to all Rudder commands added

#5 Updated by Alexandre Anriot 12 months ago

Thanks for the ticket Nicolas.

Nicolas CHARLES wrote:

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 ...)

#6 Updated by Benoît PECCATTE 12 months ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE

#7 Updated by Benoît PECCATTE 12 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1162

#8 Updated by Benoît PECCATTE 12 months ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#9 Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.3 and 4.1.0~beta3 which were released today.

Also available in: Atom PDF