Project

General

Profile

Bug #14061

Agent run errors are not outputed on stderr anymore

Added by Alexis MOUSSET 14 days ago. Updated 5 days ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

Since a refactoring in CFEngine, our patch is not enough to display errors on stderr.


Related issues

Related to ncf - Bug #13931: Unparsable technique when Rudder server hostname is not in the /etc/hostsRejected

Associated revisions

Revision 4fa45e16 (diff)
Added by Alexis Mousset 14 days ago

Fixes #14061: Errors are not outputed on stderr anymore

History

#1 Updated by Alexis MOUSSET 14 days ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#2 Updated by Alexis MOUSSET 14 days ago

  • Status changed from In progress to New
  • Assignee deleted (Alexis MOUSSET)
  • Target version changed from 4.1.18 to 4.3.8

#3 Updated by Alexis MOUSSET 14 days ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#4 Updated by Alexis MOUSSET 14 days 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

#5 Updated by Alexis MOUSSET 14 days ago

  • Related to Bug #13931: Unparsable technique when Rudder server hostname is not in the /etc/hosts added

#6 Updated by Anonymous 14 days ago

  • Status changed from Pending technical review to Pending release

#7 Updated by Vincent MEMBRÉ 6 days ago

  • Subject changed from Errors are not outputed on stderr anymore to Agent run errors are not outputed on stderr anymore

#8 Updated by Vincent MEMBRÉ 5 days 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

Also available in: Atom PDF