Bug #17423: Directives file content et audit - Rudder - Issue Tracker

Actions

Bug #17423

open

Directives file content et audit

Added by Patrice ROUX over 4 years ago. Updated 5 months ago.

Status:

New

Priority:

N/A

Assignee:

-

Category:

Techniques

Target version:

Pull Request:

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Priority:

0

Name check:

To do

Fix check:

To do

Regression:

Description

Bonjour,

Dans la directive "File Content", si je coche la partie "replace content" pour imposer le contenu d'un fichier de config, je me retrouve en permanence avec un "non compliant".
Cela est apparu suite à mon upgrade depuis la 4.3.10 -> 5.0.17 -> 6.0.5 -> 6.1.0 beta 3.

Mes fichiers cibles sont pourtant tous correcte car si je passe en "enforce", j'ai un retour "compliant" et dés que je repasse en audit, je me retrouve avec "non-compliant".

Cela fausse grandement ma visu de conformité de mes serveurs...

Une idée?

patrice ROUX

Actions

#1

Updated by François ARMAND over 4 years ago

Category changed from Agent to Techniques
Target version changed from Ideas (not version specific) to 6.1.2
User visibility set to Operational - other Techniques | Rudder settings | Plugins
Priority changed from 0 to 51

Actions

#2

Updated by Nicolas CHARLES over 4 years ago

I can totally reproduce this

Actions

#3

Updated by Nicolas CHARLES over 4 years ago

Target version changed from 6.1.2 to 6.0.8

I tried on a 6.0.6 server and I also have the error
With a 6.0.3 agent i still have the error

Actions

#4

Updated by Nicolas CHARLES over 4 years ago

i checked with both version 7.0 and 8.0 of the technique, both are failing.

Actions

#5

Updated by Nicolas CHARLES over 4 years ago

this is because empty_file_before_editing set to true with a dry-run mode fails: it starts with a blank state and pretend to add lines, which fails

Actions

#6

Updated by Nicolas CHARLES over 4 years ago

it does not work either with a 5.0.16 agent

Actions

#7

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.0.8 to 6.0.9

Actions

#8

Updated by Vincent MEMBRÉ about 4 years ago

Target version changed from 6.0.9 to 6.0.10
Priority changed from 51 to 49

Actions

#9

Updated by Vincent MEMBRÉ about 4 years ago

Target version changed from 6.0.10 to 798
Priority changed from 49 to 48

Actions

#10

Updated by Benoît PECCATTE over 3 years ago

Target version changed from 798 to 6.1.14
Priority changed from 48 to 43

Actions

#11

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 6.1.14 to 6.1.15

Actions

#12

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 6.1.15 to 6.1.16

Actions

#13

Updated by Vincent MEMBRÉ about 3 years ago

Target version changed from 6.1.16 to 6.1.17

Actions

#14

Updated by Vincent MEMBRÉ about 3 years ago

Target version changed from 6.1.17 to 6.1.18

Actions

#15

Updated by Vincent MEMBRÉ almost 3 years ago

Target version changed from 6.1.18 to 6.1.19

Actions

#16

Updated by Vincent MEMBRÉ over 2 years ago

Target version changed from 6.1.19 to 6.1.20

Actions

#17

Updated by Vincent MEMBRÉ over 2 years ago

Target version changed from 6.1.20 to 6.1.21

Actions

#18

Updated by Vincent MEMBRÉ over 2 years ago

Target version changed from 6.1.21 to old 6.1 issues to relocate

Actions

#19

Updated by Alexis Mousset 7 months ago

Target version changed from old 6.1 issues to relocate to 7.3.15
Priority changed from 43 to 0

Actions

#20

Updated by Vincent MEMBRÉ 6 months ago

Target version changed from 7.3.15 to 7.3.16

Actions

#21

Updated by Vincent MEMBRÉ 5 months ago

Target version changed from 7.3.16 to 7.3.17

Actions

Also available in: Atom PDF