Project

General

Profile

Actions
Copy link

User story #3137

closed

Using certains CFEngine variables in directives may lead to unexpected errors in the promises generation

Added by Nicolas CHARLES almost 12 years ago. Updated over 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
2.5.0~rc1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

When using ${sys.fqhost} in the "On which host name is the virtual host to be reachable:" field for the apache2 technique, the promises cannot be generated, and we have the following error

=> Error when processing rule (0637971f-25dd-4286-93bd-7afcc5c9b1df/apacheServer:1.0/07ec78fa-5158-469c-960c-f5b825e29b18) with variables: Stream(APACHE_TRACEENABLE Should the server allow the use of the TRACE method (TraceEnable) : ArrayBuffer(Off), ?)

Exists on 2.4, probably happens on 2.3 also

The issue is that ${xxx.xxx} refers to internal Rudder variable, that rudder tries to resolves.
We should change this internal syntax to ${rudder.xxx.xxx}

Subtasks 2 (0 open — 2 closed)

User story #3149: Change the internal Rudder variables syntax from ${xxx.yyy} to ${rudder.xxx.yyy}ReleasedFrançois ARMAND2013-01-08Actions
User story #3153: Update the LDAP init script to use the new internal Rudder variable formatReleasedNicolas CHARLES2013-01-08Actions
Actions
Copy link

Also available in: Atom PDF