Project

General

Profile

Actions

Bug #3730

closed

Cron on RHEL/CentOS and Ubuntu nodes was not checked with initial promises

Added by Jonathan CLARKE over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
3
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

Similar to #3609, cf-agent tries to check that cron is running when the initial promises are run (this happens when a node just got rudder-agent installed, but has not yet been accepted by the Rudder server). On RHEL/CentOS systems, this fails as follows:

 -> Making a one-time restart promise for /usr/sbin/cron$
Proposed executable file "/etc/init.d/cron" doesn't exist
/etc/init.d/cron restart promises to be executable but isn't
I: Report relates to a promise with handle "" 
I: Made in version 'not specified' of '/var/rudder/cfengine-community/inputs/promises.cf' near line 372
I: Comment: Restarting crond

Note: this may also happen on ubuntu systems.

I will "port" the fix from #3609 to initial promises.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #3609: Cron on RHEL/CentOS nodes was restarted at every execution of CFEngineReleasedNicolas PERRON2013-05-24Actions
Actions #1

Updated by Jonathan CLARKE over 9 years ago

  • Subject changed from Cron on RHEL/CentOS nodes was not checked with initial promises to Cron on RHEL/CentOS and Ubuntu nodes was not checked with initial promises
  • Priority changed from 2 to 3
Actions #2

Updated by Jonathan CLARKE over 9 years ago

  • Status changed from In progress to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:b7694555012e20833526a23b1ff721e688cee8dd.

Actions #3

Updated by Jonathan CLARKE over 9 years ago

Applied in changeset policy-templates:commit:bb8ab8f23a9cd8350ef89010a9d2514e44e02eb3.

Actions #4

Updated by Jonathan CLARKE over 9 years ago

TR done by Nicolas Perron.

Actions #5

Updated by Jonathan CLARKE over 9 years ago

  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/149
Actions #6

Updated by Nicolas PERRON over 9 years ago

  • Status changed from Pending release to Released
Actions #7

Updated by Nicolas PERRON over 9 years ago

This bug has been fixed in Rudder 2.4.7, which was released today.
Check out:

Actions

Also available in: Atom PDF