Actions
Bug #12812
open
Wrong reports on "File content" when using undefined variables
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
I tried to use file content with a call to a undefined variable on rudder 4.3.3
In file content:
file: /tmp/fda
value: ${my_prefix.my_name}
enforce: true
I end up with a GM reporting "compliant", not a repaired one, creating the file /tmp/fda with the following content:
${my_prefix.my_name}
I was expecting an error report, or at least a repaired and a warning.
Updated by François ARMAND over 6 years ago
- Subject changed from Wrong reports on "File content" when using undefined variables to Wrong reports on "File content" when using undefined variables
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Priority changed from 0 to 67
This a behavior of CFEngine, hard to change. It's reported here: https://tracker.mender.io/browse/CFE-1907?jql=text%20~%20%22undefined%20variable%22
Moreover, its behavior changed in 3.10 and perhaps you see something special here. Alexis, could you take a look at it?
Updated by 
Updated by 
Updated by
Actions