Actions
Bug #3332
closed
Using parametrized variables based on Rules values fails
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When we use Rudder variables based on values defined in others Rules, the deployment fails because Rudder cannot find the target value
Updated by Nicolas CHARLES almost 12 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
The pull request is there
https://github.com/Normation/rudder/pull/136
Updated by Nicolas CHARLES almost 12 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset cdf9b303bf8c0b23d2823ecf6d2df182cd5e1abf.
Updated by Anonymous almost 12 years ago
Applied in changeset c7b81117f39e53a7f88761dedf80e016d008234c.
Updated by Vincent MEMBRÉ almost 12 years ago
There is a None implicity casted as to Empty, I made another pull request to correct that and also clear the log message (ids are displayed with their class, we should only display the value)
Updated by Matthieu CERDA over 11 years ago
- Status changed from Pending release to Released
This ticket has been adressed in the 2.3.11 release of Rudder.
The ChangeLog is available here: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog23
Actions