Project

General

Profile

Bug #11600

Result class containing {} are not properly canonized

Added by Janos Mattyasovszky over 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Technique editor - API
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
63

Description

The following command within a "Command execution result" method:

rpm -q --qf '%{VERSION}-%{RELEASE}' rudder-agent 

Generates resulting classes with following base:

command_execution_result_rpm__q___qf___{VERSION}__{RELEASE}__rudder_agent

=> The {} chars did not get canonized.


Subtasks

Bug #12097: parent patch broke testsReleasedBenoît PECCATTEActions
Bug #12102: Parent patch broke tests (again)ReleasedBenoît PECCATTEActions
Bug #12114: parent patch broke testsReleasedVincent MEMBRÉActions

Related issues

Related to Rudder - Bug #11210: NCF Variable expansion on node properties does not workNewActions
Related to Rudder - Bug #10304: Broken variable expression when using node properties in the technique editorReleasedActions
Is duplicate of ncf - Bug #8586: Wrong definition of class condition if we use a variable with [ ] in itRejectedActions

Associated revisions

Revision c9125aba (diff)
Added by Benoît PECCATTE over 1 year ago

Fixes #11600: Result class containing {} are not properly canonized

History

#1

Updated by Alexis MOUSSET over 1 year ago

  • Subject changed from Result class not properly canonized to Result class containing {} are not properly canonized
  • Category set to Technique editor - API
  • Target version set to 0.x
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Effort required set to Small
  • Priority changed from 0 to 55
#2

Updated by Nicolas CHARLES over 1 year ago

  • Related to Bug #11210: NCF Variable expansion on node properties does not work added
#3

Updated by Nicolas CHARLES over 1 year ago

  • Related to Bug #10304: Broken variable expression when using node properties in the technique editor added
#5

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 0.x to 3.1.25
#6

Updated by Benoît PECCATTE over 1 year ago

  • Priority changed from 55 to 67
#7

Updated by François ARMAND over 1 year ago

  • Assignee set to Vincent MEMBRÉ
#8

Updated by Benoît PECCATTE over 1 year ago

  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
  • Priority changed from 67 to 66
#9

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.25 to 387
#10

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 387 to 4.1.10
#11

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from New to In progress
  • Priority changed from 66 to 64
#12

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/ncf/pull/691
#13

Updated by Benoît PECCATTE over 1 year ago

  • Is duplicate of Bug #8586: Wrong definition of class condition if we use a variable with [ ] in it added
#14

Updated by Rudder Quality Assistant over 1 year ago

  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
#15

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from Pending technical review to Pending release
#16

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released
  • Priority changed from 64 to 63

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Also available in: Atom PDF