Bug #14061
closed
Agent run errors are not outputed on stderr anymore
Added by Alexis Mousset almost 6 years ago.
Updated almost 6 years ago.
Description
Since a refactoring in CFEngine, our patch is not enough to display errors on stderr.
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to New
- Assignee deleted (
Alexis Mousset)
- Target version changed from 4.1.18 to 4.3.8
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- 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
- Related to Bug #13931: Unparsable technique when Rudder server hostname is not in the /etc/hosts added
- Status changed from Pending technical review to Pending release
- Subject changed from Errors are not outputed on stderr anymore to Agent run errors are not outputed on stderr anymore
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.8 and 5.0.4 which were released today.
Changelog
Changelog
- Related to Bug #14692: Rudder agent check does not repair policies if they are broken added
- Related to Bug #18178: Unparsable techniques when there are error in cf-promises (cf-promises outputs error in stdout) added
Also available in: Atom
PDF
Updated by 
Updated by Anonymous 
Updated by 
Updated by