Project

General

Profile

Actions

Bug #16012

closed

Bug #14559: Invalid cron file put by packaging

error at run of rudder-agent once it's bootstrapped (and invalid cron) on Debian 9

Bug #16012: error at run of rudder-agent once it's bootstrapped (and invalid cron) on Debian 9

Added by Nicolas CHARLES about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

E| compliant     Common                    Security parameters                          The internal environment security is acceptable
   error: Template file '/var/rudder/cfengine-community/inputs/common/cron/rudder-agent-community-cron' could not be opened for reading
   error: Method 'setup_cronjob' failed in some repairs
E| compliant     Common                    CRON Daemon                                  Cron daemon status was correct

the file indeed doesn't exists (but rudder-agent-nova-cron does exist)
and the cron file set by packaging is invalid

# cat /etc/cron.d/rudder-agent 
# Cron file for Rudder
#
# Will manually run cf-agent in case cf-execd is no longer running. cf-agent will fire up a new cf-execd.
#
# To temporarily avoid this behaviour, run 'rudder agent disable'

{{#classes.slackware}}
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/rudder/bin/rudder agent check -q >> /var/log/rudder/agent-check/check.log 2>&1
{{/classes.slackware}}
{{^classes.slackware}}
0,5,10,15,20,25,30,35,40,45,50,55 * * * * root /opt/rudder/bin/rudder agent check -q >> /var/log/rudder/agent-check/check.log 2>&1
{{/classes.slackware}}

Updated by Nicolas CHARLES about 6 years ago Actions #1

  • Category changed from System techniques to Packaging

moving the ticket to packaging, as the code generating the inital promises looks ok

Updated by Nicolas CHARLES about 6 years ago Actions #2

cron creation is

echo ""# Cron file for Rudder # # Will manually run cf-agent in case cf-execd is no longer running. cf-agent will fire up a new cf-execd. # # To temporarily avoid this behaviour, run 'rudder agent disable'   0,5,10,15,20,25,30,35,40,45,50,55 * * * * root /opt/rudder/bin/rudder agent check -q >> /var/log/rudder/agent-check/check.log 2>&1"" > initial-promises/node-server/common/cron/rudder-agent-community-cron
# Cron file for Rudder

Updated by Nicolas CHARLES about 6 years ago Actions #3

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES

Updated by Nicolas CHARLES about 6 years ago Actions #4

  • Category deleted (Packaging)
  • Target version deleted (6.0.0~beta1)
  • Name check deleted (To do)

Updated by Nicolas CHARLES about 6 years ago Actions #5

  • Target version set to 5.0.15

retargetting to 5.0, linked to #14559

Updated by Nicolas CHARLES about 6 years ago Actions #6

  • Parent task set to #14559

Updated by Nicolas CHARLES about 6 years ago Actions #7

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Félix DALLIDET
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/2125

Updated by Nicolas CHARLES about 6 years ago Actions #8

  • Status changed from Pending technical review to Pending release

Updated by Félix DALLIDET about 6 years ago Actions #9

  • Category set to Packaging

Updated by Vincent MEMBRÉ about 6 years ago Actions #10

  • Name check set to To do

Updated by Alexis Mousset about 6 years ago Actions #11

  • Name check changed from To do to Reviewed

Updated by Alexis Mousset about 6 years ago Actions #12

  • Fix check changed from To do to Checked

Updated by Vincent MEMBRÉ about 6 years ago Actions #13

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.15 which was released today.

Actions

Also available in: PDF Atom