Project

General

Profile

Actions

Bug #18178

closed

Unparsable techniques when there are error in cf-promises (cf-promises outputs error in stdout)

Added by Nicolas CHARLES over 3 years ago. Updated over 3 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

In #13931 we had unparsable techniques when hostname was not set, because cf-promises outputed errors to stdout
we fixed that in #14061, yet in 6.1 the path is gone

We need to correct that again, as it prevent having techniques in technique editor


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #14061: Agent run errors are not outputed on stderr anymoreReleasedBenoît PECCATTEActions
Actions #1

Updated by Nicolas CHARLES over 3 years ago

  • Related to Bug #14061: Agent run errors are not outputed on stderr anymore added
Actions #2

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions #3

Updated by Vincent MEMBRÉ over 3 years ago

  • Assignee changed from Vincent MEMBRÉ to Alexis Mousset
  • Pull Request set to https://github.com/Normation/ncf/pull/1240
Actions #4

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from In progress to Pending release

Applied in changeset ncf:commit:10b72ee4f0540be0241dbb6bd8c8c7aeccc08ed2.

Actions #5

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.5 to 6.1.4
Actions #6

Updated by Vincent MEMBRÉ over 3 years ago

  • Fix check changed from To do to Checked
Actions #7

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.4 which was released today.

Actions

Also available in: Atom PDF