Actions
Bug #13931
closed
Unparsable technique when Rudder server hostname is not in the /etc/hosts
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Web - Technique editor
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
We are disabling DNS queries in parsing of user generated technique. However, in this case, we rely on a valid entry in /etc/hosts
If it's not the case, parsing fails with
caused by : No JSON object could be decoded ERROR: Could not parse Technique 'test_var' caused by : An error occured while parsing technique '/var/rudder/configuration-repository/ncf/50_techniques/test_var/test_var.cf'
cause is cf-promises outputs "error: Unable to resolve policy server host: orchestrateur-3.labo.normation.com"
to make matter worse, this is outputed on STDOUT rather than STDERR
removing the RES_OPTIONS='attempts:0' solves the issue
Updated by Nicolas CHARLES about 6 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/879
Updated by Alexis Mousset almost 6 years ago
- Status changed from Pending technical review to Rejected
This fix would trigger dns timeouts which we do not want. The issue will be fixed by #14061.
Updated by Alexis Mousset almost 6 years ago
- Related to Bug #14061: Agent run errors are not outputed on stderr anymore added
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category changed from Technique editor - API to Web - Technique editor
Actions