Project

General

Profile

Actions

Bug #5644

closed

We can't search for "Name =" for an environment variable name in node

Bug #5644: We can't search for "Name =" for an environment variable name in node

Added by Benoît PECCATTE almost 12 years ago. Updated over 11 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When in the "Node Management > Search Node" page, if you search using "Environment Variables > Name=Value > Is Defined", you can't type a variable name.

Updated by François ARMAND over 11 years ago Actions #1

  • Priority changed from N/A to 3

Ah, interesting. Typical non adaptation to change.

I confirm, the cause it that in all other case, "is defined" is just a zero-arg function, but here it is a 1 arg. As environment variables were added after all the machinery was built, the machinery didn't took into account that "is defined" could be a 1-arg function.

Updated by Vincent MEMBRÉ over 11 years ago Actions #2

  • Target version changed from 2.6.19 to 2.6.20

Updated by François ARMAND over 11 years ago Actions #3

  • Subject changed from In search node searching if a variable is defined is disabled to We can't search for "is defined" for an environment variable name in node
  • Status changed from New to In progress
  • Target version changed from 2.6.20 to 2.10.8

Updated by François ARMAND over 11 years ago Actions #4

  • Assignee set to François ARMAND

Updated by François ARMAND over 11 years ago Actions #5

  • Subject changed from We can't search for "is defined" for an environment variable name in node to We can't search for "Name =" for an environment variable name in node

Updated by François ARMAND over 11 years ago Actions #6

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Priority changed from 3 to 1 (highest)
  • Pull Request set to https://github.com/Normation/rudder/pull/712

Updated by François ARMAND over 11 years ago Actions #7

  • Pull Request changed from https://github.com/Normation/rudder/pull/712 to https://github.com/Normation/rudder/pull/713

Updated by François ARMAND over 11 years ago Actions #8

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

Updated by Vincent MEMBRÉ over 11 years ago Actions #10

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.8 and 2.11.5, which were released today (16/12/14)

Actions

Also available in: PDF Atom