Project

General

Profile

Actions

Bug #10418

closed

Bug #10379: When upgrading to 4.1, rudder.community.checkpromises.command=/bin/true option is lost

checkpromise+sighup config should be commented in properties file and bad name of corresponding hook

Added by François ARMAND over 7 years ago. Updated about 7 years ago.

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

Description

As explain in comment in the parent task, they are no more used and it is misleading to keep them uncommented. And it breaks the migration script logic.

Actions #1

Updated by François ARMAND over 7 years ago

  • Assignee set to François ARMAND
Actions #2

Updated by François ARMAND over 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder/pull/1586
Actions #3

Updated by François ARMAND over 7 years ago

  • Subject changed from checkpromise config should be commented in properties file to checkpromise+sighup config should be commented in properties file and bad name of corresponding hook
Actions #4

Updated by François ARMAND over 7 years ago

Also, file "/opt/rudder/hooks.d/policy-generation-finished/50-sigup-cf-serverd" should be named "/opt/rudder/hooks.d/policy-generation-finished/50-reload-policy-file-server"

Actions #5

Updated by François ARMAND over 7 years ago

  • Status changed from Pending technical review to Pending release
Actions #6

Updated by Benoît PECCATTE about 7 years ago

  • Status changed from Pending release to Released
  • Priority set to 0

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

Actions

Also available in: Atom PDF