Bug #11883
closed
Bug #11870: rudder_reporting file is invalid on nodes if it contains '&&' in one of its parameter
wrong path to rudder_reporting.cf file in metata.xml generated for ncf method
Added by Vincent MEMBRÉ about 7 years ago.
Updated almost 7 years ago.
Category:
Web - Config management
Description
It misses a / between the version of the technique and the name of the rudder_reporting file
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Subject changed from rudder_reporting file is invalid on nodes if it contains '&&' in one of its parameter to wrong path to rudder_reporting.cf file in metata.xml generated for ncf method
No problme in fact , ncf was not updated on the test machine, still generating a .st instead of .cf ....
- Status changed from In progress to Rejected
- Description updated (diff)
- Status changed from Rejected to New
- Target version changed from 4.2.4 to 4.1.10
In fact the issue exists on version 4.1, reopening it
- Parent task deleted (
#11871)
- Parent task set to #11870
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/706
- Status changed from Pending technical review to Pending release
Applied in changeset ncf:commit:19d564daf900c0691647a4db050e6b68a6f58af7.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.
Also available in: Atom
PDF
Updated by