Project

General

Profile

Actions
Copy link

Bug #3332

closed

Using parametrized variables based on Rules values fails

Bug #3332: Using parametrized variables based on Rules values fails

Added by Nicolas CHARLES almost 13 years ago. Updated almost 13 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
2.3.11
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 13 years ago Actions
Copy link
 #1

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND

Updated by Nicolas CHARLES almost 13 years ago Actions
Copy link
 #2

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Updated by Anonymous almost 13 years ago Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 13 years ago Actions
Copy link
 #4

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)

https://github.com/Normation/rudder/pull/139

Updated by Matthieu CERDA almost 13 years ago Actions
Copy link
 #5

  • 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
Copy link

Also available in: PDF Atom