Actions
Bug #6845
closedNodes using syslogd coninue to report to their old server when changing their policy server
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The title says it all:
Let say i have:
- a Server
- a node linked to the server and based on Centos5
- a relay
/etc/syslog.conf looks like this:
local6.notice @server
If i switch my node to be under the relay, the syslog conf will chenge to:
local6.notice @server local6.notice @relay
Making the node reporting bith to the server and the relay, having 2 reports at the end on the Server
We should change the deletion condition in promises.cf (ligne 768):
some ideas:
- Replacing both delete lines by: "^local6(\..*)?\s+(?!${syslogd}).*" (more complex but more like we want to achieve
- Delete all lines stating by local6
In both cases keep the adding line
This can be impreved by only editing a section of the file between two tags (so we don't delete other local6 attempts)
Updated by Vincent MEMBRÉ over 9 years ago
- Project changed from Rudder tools to Rudder
- Category set to System techniques
- Target version set to 2.10.15
Updated by Matthieu CERDA over 9 years ago
- Status changed from New to In progress
Updated by Matthieu CERDA over 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/706
Updated by Matthieu CERDA over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-techniques|0928f9ac808a4b892915612cec60dc3253776418.
Updated by Benoît PECCATTE over 9 years ago
Applied in changeset rudder-techniques|5006816a07dc045c944f47934651fc6c2f6628f6.
Updated by Vincent MEMBRÉ over 9 years ago
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
Actions