Bug #18536
closed
File_augeas_set method does not report as expected
Added by Félix DALLIDET about 4 years ago.
Updated over 2 years ago.
Fix check:
Error - Blocking
Description
The methode never reports a repaired. Also, it does not seem to define any class_prefix
Related issues
1 (1 open — 0 closed)
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/1262
- Status changed from Pending technical review to Pending release
Applied in changeset commit:ef2654e87c19c23b6db870fceac13e74f207e304.
- Fix check changed from To do to Error - Blocking
it does not report a repair when using
"File Augeas set_${report_data.directive_id}_0" usebundle => file_augeas_set("/var/lib/pgsql/data/postgresql.conf/work_mem", "2MB", "", ""),
if => concat("any");
This bug has been fixed in Rudder 6.1.7 which was released today.
This bug has been fixed in Rudder 6.1.7 and 6.2.1 which were released by the end of October 2020.
- Related to Bug #18648: File Augeas set does not always report repair added
- Status changed from Pending release to Released
- Project changed from 41 to Rudder
- Category changed from Generic methods - File Management to Generic methods
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by