Actions
Bug #22059
closedfile_augeas_commands method fails to detect failures and changes
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
54
Name check:
To do
Fix check:
To do
Regression:
No
Description
The method uses the execresult
keyword to call augtool and captures its output to the given variable name.
But the method always return a success even when executing augeas commands with syntax errors.execresult
is not able to catch the exit code, we should at least properly document that the method only reports success and try to fix it in 7.3 when we should be able to
better interact with third-party tools using custom resources.
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.2.2 to 7.2.3
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.3 to 7.2.4
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.4 to 7.2.5
- Priority changed from 56 to 55
Updated by Alexis Mousset almost 2 years ago
- Status changed from New to Rejected
- Priority changed from 55 to 54
Updated by Alexis Mousset almost 2 years ago
- Is duplicate of Bug #22060: file_augeas_commands method fails to detect failures and changes added
Actions