Bug #13619
closed
Document that resource file of Techniques are shared to nodes with UTF-8 Encoding *only* (breaks for other encoding)
Added by Nicolas CHARLES over 5 years ago.
Updated almost 5 years ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Description
somehow, the Rudder-Agent.xml in the generated promises starts with ef bf bd ef bf bd BOM, while the original file starts with ff fe BOM
result is: file is corrupted.
BOM of original file was removed, as a workaround, in #13616, but we need to understand WHY it happened
Hypothesis: scala lib interpreting and adding the BOM, some side effect of #12471, or something else.
- Target version changed from 4.3-1.11 to 4.3-1.12
- Project changed from 78 to Rudder
- Subject changed from UTF-8 encoding BOM added to Rudder-Agent.xml file by rudder dsc plugin to Resource file of Techniques are shared to nodes with UTF-8 Encoding
- Category changed from System techniques to System techniques
- Target version changed from 4.3-1.12 to 4.3.5
- Category changed from System techniques to Web - Config management
- Target version changed from 4.3.5 to 4.3.6
- Target version changed from 4.3.6 to 4.3.7
Here, we need to either document that fact or add an "input encoding" and "output encoding" parameter for resource files.
- Subject changed from Resource file of Techniques are shared to nodes with UTF-8 Encoding to Resource file of Techniques are shared to nodes with UTF-8 Encoding *only* (breaks for other encoding)
- Target version changed from 4.3.7 to 4.3.8
- Target version changed from 4.3.8 to 4.3.9
- Target version changed from 4.3.9 to 4.3.10
- Target version changed from 4.3.10 to 4.3.11
- Target version changed from 4.3.11 to 4.3.12
- Subject changed from Resource file of Techniques are shared to nodes with UTF-8 Encoding *only* (breaks for other encoding) to Document that resource file of Techniques are shared to nodes with UTF-8 Encoding *only* (breaks for other encoding)
- Category changed from Web - Config management to Documentation
- Target version changed from 4.3.12 to 5.0.10
- Severity changed from Critical - prevents main use of Rudder | no workaround | data loss | security to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
- Effort required set to Very Small
- Priority changed from 0 to 90
So, the possibility to add file encoding for all templates is a long term new feature. In the meantime, we need to just clearly document the limitation (it should be ok for most use case, and workaroundable for all even if it supposes a very tedious step of transcoding on the node).
- Assignee set to Nicolas CHARLES
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-doc/pull/578
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
- Priority changed from 90 to 89
This bug has been fixed in Rudder 5.0.10 which was released today.
- Related to Bug #19222: Policy generation does change technique resource files when it should not added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by