Actions
Bug #18536
closedFile_augeas_set method does not report as expected
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Error - Blocking
Regression:
Description
The methode never reports a repaired. Also, it does not seem to define any class_prefix
Updated by Félix DALLIDET about 4 years ago
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
Updated by Félix DALLIDET about 4 years ago
- 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
Updated by Félix DALLIDET about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:ef2654e87c19c23b6db870fceac13e74f207e304.
Updated by Nicolas CHARLES about 4 years ago
- 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");
Updated by Vincent MEMBRÉ almost 4 years ago
This bug has been fixed in Rudder 6.1.7 which was released today.
Updated by Vincent MEMBRÉ over 3 years ago
This bug has been fixed in Rudder 6.1.7 and 6.2.1 which were released by the end of October 2020.
Updated by Vincent MEMBRÉ over 3 years ago
- Related to Bug #18648: File Augeas set does not always report repair added
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category changed from Generic methods - File Management to Generic methods
Actions