Project

General

Profile

Actions

Bug #3332

closed

Using parametrized variables based on Rules values fails

Added by Nicolas CHARLES over 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:

Description

When we use Rudder variables based on values defined in others Rules, the deployment fails because Rudder cannot find the target value

Actions #1

Updated by Nicolas CHARLES over 9 years ago

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

Updated by Nicolas CHARLES over 9 years ago

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

Updated by Anonymous over 9 years ago

Actions #4

Updated by Vincent MEMBRÉ over 9 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)

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

Actions #5

Updated by Matthieu CERDA about 9 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

Also available in: Atom PDF