Actions
Bug #14061
closedAgent run errors are not outputed on stderr anymore
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Since a refactoring in CFEngine, our patch is not enough to display errors on stderr.
Updated by Alexis Mousset almost 6 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset almost 6 years ago
- Status changed from In progress to New
- Assignee deleted (
Alexis Mousset) - Target version changed from 4.1.18 to 4.3.8
Updated by Alexis Mousset almost 6 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1754
Updated by Alexis Mousset almost 6 years ago
- Related to Bug #13931: Unparsable technique when Rudder server hostname is not in the /etc/hosts added
Updated by Anonymous almost 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|4fa45e16b1a62867b9b74d1478040ae26564f0c3.
Updated by Vincent MEMBRÉ almost 6 years ago
- Subject changed from Errors are not outputed on stderr anymore to Agent run errors are not outputed on stderr anymore
Updated by Vincent MEMBRÉ almost 6 years ago
- Status changed from Pending release to Released
Updated by Nicolas CHARLES over 5 years ago
- Related to Bug #14692: Rudder agent check does not repair policies if they are broken added
Updated by Nicolas CHARLES about 4 years ago
- Related to Bug #18178: Unparsable techniques when there are error in cf-promises (cf-promises outputs error in stdout) added
Actions