Project

General

Profile

Actions

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.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
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.


Related issues 3 (0 open3 closed)

Related to Rudder - Bug #13931: Unparsable technique when Rudder server hostname is not in the /etc/hostsRejectedAlexis MoussetActions
Related to Rudder - Bug #14692: Rudder agent check does not repair policies if they are broken ReleasedNicolas CHARLESActions
Related to Rudder - Bug #18178: Unparsable techniques when there are error in cf-promises (cf-promises outputs error in stdout)ReleasedAlexis MoussetActions
Actions #1

Updated by Alexis Mousset almost 6 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions #2

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
Actions #3

Updated by Alexis Mousset almost 6 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions #4

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
Actions #5

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
Actions #6

Updated by Anonymous almost 6 years ago

  • Status changed from Pending technical review to Pending release
Actions #7

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
Actions #8

Updated by Vincent MEMBRÉ almost 6 years ago

  • 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
Actions #9

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #14692: Rudder agent check does not repair policies if they are broken added
Actions #10

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

Also available in: Atom PDF