Bug #18178
closed
Unparsable techniques when there are error in cf-promises (cf-promises outputs error in stdout)
Added by Nicolas CHARLES about 4 years ago.
Updated about 4 years ago.
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 to Bug #14061: Agent run errors are not outputed on stderr anymore added
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Assignee changed from Vincent MEMBRÉ to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/1240
- Status changed from In progress to Pending release
Applied in changeset ncf:commit:10b72ee4f0540be0241dbb6bd8c8c7aeccc08ed2.
- Target version changed from 6.1.5 to 6.1.4
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.4 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by