Project

General

Profile

Actions

Bug #19222

closed

Policy generation does change technique resource files when it should not

Added by Félix DALLIDET about 3 years ago. Updated almost 3 years ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
70
Name check:
To do
Fix check:
Checked
Regression:

Description

When adding a resource to a technique the generation process modifies it, it should not change the file at all since this prevent any binary deployment and can break several things.

File before uploading:

fdallidet@fda /tmp%md5sum packages-microsoft-prod.deb                                                                                                                                 ~> 11:33
bacf11bbcf9071983e2aba39a32c569d  packages-microsoft-prod.deb

In the technique folder on the server the hash is correct.
In the policy folder for each node, the hash is incorrect.

I will use the old shared-files feature as a workaround until fix.

It seems like the generation process is responsible here. I had the issue in 6.2.6 but it is likely to also be in 6.1


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #17685: Resources that are BOM files are not anymore on node policy directory after generationResolvedActions
Related to Rudder - Bug #13619: Document that resource file of Techniques are shared to nodes with UTF-8 Encoding *only* (breaks for other encoding)ReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF