Project

General

Profile

Actions

Bug #4674

closed

When modifying a directive based on a meta-technique with multivalued section with same component key, the duplicated component keys are removed

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

Status:
Released
Priority:
1
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

with a metatechnique that has 4 component key identical in a section, for instance

<SECTION component="true" multuvalued="true" name="File replace line">
  <REPORTKEYS>
     <VALUE>${grub.knowledge.fstab_path}</VALUE>
     <VALUE>${grub.knowledge.fstab_path}</VALUE>
     <VALUE>${grub.knowledge.fstab_path}</VALUE>
     <VALUE>${grub.knowledge.fstab_path}</VALUE>
  </REPORTKEYS>
</SECTION>

once loaded in the web interface, it transforms into 4 sections with one key in the Change request screen
When we create the directive, it is fine, but when we update the directive, it becomes

<section name="File replace line">
  <var name="expectedReportKey File replace lines">
    ${grub.knowledge.fstab_path}
  </var>
</section>

and the 3 others sections are dropped (as seen in the change request or event log)

then, report is unknown


Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #5330: When using several times a generic_method on same file with class_prefix based on filename, reports will be in "Unknown" and "No answer" statusReleasedVincent MEMBRÉ2014-07-31Actions
Actions #1

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.9.5 to 2.9.6
Actions #2

Updated by Jonathan CLARKE about 8 years ago

  • Target version changed from 2.9.6 to 2.9.7
Actions #3

Updated by Jonathan CLARKE about 8 years ago

  • Target version changed from 2.9.7 to 150
Actions #4

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 150 to 2.10.4
Actions #5

Updated by Nicolas PERRON about 8 years ago

  • Target version changed from 2.10.4 to 2.6.18
Actions #6

Updated by Nicolas PERRON about 8 years ago

  • Target version changed from 2.6.18 to 2.10.5
Actions #7

Updated by Matthieu CERDA about 8 years ago

  • Status changed from New to Released

This bug has been fixed in Rudder 2.10.4, which was released today.
Check out:

The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-August/000106.html
The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions

Also available in: Atom PDF