Project

General

Profile

Actions

Bug #6721

closed

When a node is promoted to relay, the old rsyslog conf is never replaced

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

Status:
Released
Priority:
1
Assignee:
Matthieu CERDA
Category:
Server components
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

If I promote a node to a relay, the rsyslog conf of the node will never be replaced, and will always superceed the rsyslong conf for the relay, resulting in difficult debugging, and impossibility to change policy server
Techniques for relay should purge the rudder-agent.conf file

Actions #1

Updated by Nicolas CHARLES about 7 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to Matthieu CERDA
  • Priority changed from N/A to 1
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/682
Actions #2

Updated by Nicolas CHARLES about 7 years ago

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

Updated by Matthieu CERDA about 7 years ago

Actions #4

Updated by Vincent MEMBRÉ about 7 years ago

This bug has been fixed in Rudder 2.10.15, 2.11.12, 3.0.7 and 3.1.0 which were released today.

Actions #5

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF