Bug #17685: Resources that are BOM files are not anymore on node policy directory after generation - Rudder - Issue Tracker

Actions

Copy link

Bug #17685

closed

Resources that are BOM files are not anymore on node policy directory after generation

Added by Félix DALLIDET over 4 years ago. Updated about 1 year ago.

Status:

Resolved

Priority:

N/A

Assignee:

Category:

Web - Technique editor

Target version:

old 6.1 issues to relocate

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Getting started - demo | first install | Technique editor and level 1 Techniques

Effort required:

Priority:

Name check:

To do

Fix check:

To do

Regression:

Description

I was working with a bom file from one of my windows node, and I ended up with a different file between the one
that I passed to the technique editor, and the one I received on my node.

fdallidet@fda ~%file -bi ~/Rudder/rudder-tests/localhost.mof                                                                                                                          ~> 19:59
text/plain; charset=utf-16le
fdallidet@fda ~%file -bi ~/Rudder/rudder-tests/reports/localhost.mof                                                                                                                  ~> 20:00
application/octet-stream; charset=binary

This is really annoying when dealing with small binary files for instance

Files

localhost.mof (2.02 KB) localhost.mof

Original file

Félix DALLIDET, 2020-06-10 10:37

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Félix DALLIDET over 4 years ago

File localhost.mof localhost.mof added

Update, it seems that it is the policy generation that is in cause here:

#Original file
e49ef37cd4102a543f4db74cedb4ccc9  /vagrant/originel/localhost.mof

#In the technique, server-side
e49ef37cd4102a543f4db74cedb4ccc9  resources/localhost.mof

#In the policy zip archive on the server side
1b3d7f86f56a524a96194a0050a6214b  Windows_mof/1.0/resources/localhost.mof

#In the technique on the node
1b3d7f86f56a524a96194a0050a6214b  /vagrant/localhost.mof

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.0.7 to 6.0.8

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.0.8 to 6.0.9

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

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

Actions

Copy link

Updated by Vincent MEMBRÉ about 4 years ago

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

Actions

Copy link

Updated by Benoît PECCATTE over 3 years ago

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

Actions

Copy link

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 6.1.14 to 6.1.15

Actions

Copy link

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 6.1.15 to 6.1.16

Actions

Copy link

#10

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 6.1.16 to 6.1.17

Actions

Copy link

#11

Updated by Vincent MEMBRÉ about 3 years ago

Target version changed from 6.1.17 to 6.1.18

Actions

Copy link

#12

Updated by Vincent MEMBRÉ about 3 years ago

Target version changed from 6.1.18 to 6.1.19

Actions

Copy link

#13

Updated by François ARMAND almost 3 years ago

Subject changed from Resource manager from the technique editor changes the files it managed to Resources that are BOM files are not anymore on node policy directory after generation

Actions

Copy link

#14