Project

General

Profile

Actions
Copy link

Bug #4809

closed

Technique "APT package manager configuration": Rudder file header is not added correctly in repository files

Added by Fabrice FLORE-THÉBAULT over 10 years ago. Updated about 10 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Techniques
Target version:
2.10.1
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

With rudder 2.10 (agent and server), you need to set up rudder_file_edit_header parameter to a one liner to get things working.

I noticed that my APT package manager configuration rules were always in a repaired state, after each run.

After some days, the size of the modified-files directory grew up dramatically. I noticed that /etc/apt/apt.conf.d/99rudder was modified at each run.

Emptying this file and running the agent 3 times produces this output. Exactly the problem that was present when the rudder_file_edit_header parameter was set to multiple plines:

cat /etc/apt/apt.conf.d/99rudder 
// #############################################################
// ### This file is protected by your Rudder infrastructure. ###
// ### Manually editing the file might lead your Rudder      ###
// ### infrastructure to change back the server's            ###
// ### configuration and/or to raise a compliance alert.     ###
// #############################################################

// ### This file is protected by your Rudder infrastructure. ###
// ### Manually editing the file might lead your Rudder      ###
// ### infrastructure to change back the server's            ###
// ### configuration and/or to raise a compliance alert.     ###
// #############################################################

// ### This file is protected by your Rudder infrastructure. ###
// ### Manually editing the file might lead your Rudder      ###
// ### infrastructure to change back the server's            ###
// ### configuration and/or to raise a compliance alert.     ###
// #############################################################

I reloaded the techniques, emptied the cache on the server, emptied the state directory, checked that the issue is present on several nodes and several versions of debian.

So, at the end, i guess the rudder_file_edit_header is not used as expected.

Actions
Copy link

Also available in: Atom PDF