Project

General

Profile

Bug #6660

A report is missing on system techniques when cron needs to be restartd

Added by Janos Mattyasovszky almost 6 years ago. Updated over 5 years ago.

Status:
Released
Priority:
2
Category:
System techniques
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

Having issues with the rudder-generated promises for crond on a SLES12 GA Server:

sles12# cf-agent -KICalways | grep 'default/check_cron_daemon'
2015-05-22T15:17:49+0200     info: /default/check_cron_daemon/processes/'/usr/sbin/cron$'[0]: Making a one-time restart promise for '/usr/sbin/cron$'
2015-05-22T15:17:49+0200     info: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'action'/default/command_execution/commands/'/bin/systemctl restart cron'[0]: Executing 'no timeout' ... '/bin/systemctl restart cron'
2015-05-22T15:17:49+0200     info: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'action'/default/command_execution/commands/'/bin/systemctl restart cron'[0]: Completed execution of '/bin/systemctl restart cron'
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'action'/default/command_execution/methods/'report'/default/_logger/methods/'logging'/default/_bundle_caller_two/methods/'${configuration.enabled_loggers}'[0]: A variable seems to have been used for the name of the method. In this case, the promiser also needs to contain the unique name of the method
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'action'/default/command_execution/methods/'report'/default/_logger/methods/'logging'/default/_bundle_caller_two/methods/'${configuration.enabled_loggers}'[0]: A method attempted to use a bundle '${configuration.enabled_loggers}' that was apparently not defined
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'action'/default/command_execution/methods/'report'/default/_logger/methods/'logging'[0]: Method '_bundle_caller_two' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'action'/default/command_execution/methods/'report'[0]: Method '_logger' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'action'[0]: Method 'command_execution' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'report'/default/_logger/methods/'logging'/default/_bundle_caller_two/methods/'${configuration.enabled_loggers}'[0]: A variable seems to have been used for the name of the method. In this case, the promiser also needs to contain the unique name of the method
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'report'/default/_logger/methods/'logging'/default/_bundle_caller_two/methods/'${configuration.enabled_loggers}'[0]: A method attempted to use a bundle '${configuration.enabled_loggers}' that was apparently not defined
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'report'/default/_logger/methods/'logging'[0]: Method '_bundle_caller_two' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'/default/service_action/methods/'report'[0]: Method '_logger' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'restart'[0]: Method 'service_action' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'report'/default/_logger/methods/'logging'/default/_bundle_caller_two/methods/'${configuration.enabled_loggers}'[0]: A variable seems to have been used for the name of the method. In this case, the promiser also needs to contain the unique name of the method
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'report'/default/_logger/methods/'logging'/default/_bundle_caller_two/methods/'${configuration.enabled_loggers}'[0]: A method attempted to use a bundle '${configuration.enabled_loggers}' that was apparently not defined
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'report'/default/_logger/methods/'logging'[0]: Method '_bundle_caller_two' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'/default/service_restart_if/methods/'report'[0]: Method '_logger' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'/default/service_restart/methods/'wrap'[0]: Method 'service_restart_if' failed in some repairs
2015-05-22T15:17:49+0200    error: /default/check_cron_daemon/methods/'restart_cron'[0]: Method 'service_restart' failed in some repairs

Agent:
rudder-agent-3.1.0.beta2.git201505180137-1.SLES.12.x86_64

Rootserver:
ncf-0.201504102231-1.SLES.11
ncf-api-virtualenv-3.0.4.release-1.SLES.11
rudder-agent-3.0.4.release-1.SLES.11
rudder-inventory-endpoint-3.0.4.release-1.SLES.11
rudder-inventory-ldap-3.0.4.release-1.SLES.11
rudder-jetty-3.0.4.release-1.SLES.11
rudder-plugin-external-node-information-2.11.4-1
rudder-reports-3.0.4.release-1.SLES.11
rudder-server-root-3.0.4.release-1.SLES.11
rudder-techniques-3.0.4.release-1.SLES.11
rudder-webapp-3.0.4.release-1.SLES.11

#1

Updated by Matthieu CERDA almost 6 years ago

  • Priority changed from N/A to 2

Thank you Janos, let's take a look at this! :)

#2

Updated by Matthieu CERDA over 5 years ago

  • Assignee set to Alexis MOUSSET

I know for sure that Alexis is working on at least this cron part on systemd-using OSes, assigning to him just in case.

#3

Updated by Alexis MOUSSET over 5 years ago

It is a reporting problem, moving the call to the configuration bundle before check_cron_daemon in promises.st seems to fix the issue. Unsure about how to properly fix it though.

#4

Updated by Matthieu CERDA over 5 years ago

  • Target version set to 2.10.16
#5

Updated by Matthieu CERDA over 5 years ago

  • Status changed from New to In progress
  • Assignee changed from Alexis MOUSSET to Matthieu CERDA
#6

Updated by Matthieu CERDA over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/716
#7

Updated by Matthieu CERDA over 5 years ago

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

Updated by Vincent MEMBRÉ over 5 years ago

  • Subject changed from SLES12 policy for restart cron throws errors to A report is missing on system techniques when cron needs to be restartd
  • Category changed from Techniques to System techniques
#10

Updated by François ARMAND over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.16, 2.11.13, 3.0.8 and 3.1.1 which were released today.

Also available in: Atom PDF