Project

General

Profile

Actions
Copy link

Bug #5330

closed

When using several times a generic_method on same file with class_prefix based on filename, reports will be in "Unknown" and "No answer" status

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" status

Added by Nicolas PERRON almost 12 years ago. Updated almost 12 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - Compliance & node report
Target version:
2.10.4
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

With several generic_method on same file with class_prefix based on filename, the expected reports generated will be OK but Rudder will not be able to analyze them correctly. The state will be 'Unknown' and 'No Answer' as Rudder will consider them as one unique report.

An example is the use of generic_method 'file_ensure_line_present_in_ini_section' twice on a file /tmp/foo.

Related issues 4 (0 open — 4 closed)

Related to Rudder - Bug #4806: When two techniques generated with ncf-builder use the same generic method with same parameters, reporting cannot dinstinguish them, and reports "Unknown"ReleasedBenoît PECCATTEActions
Related to Rudder - Bug #4797: When using multiple times the same generic method on the same object, the reporting will be broken for all of themRejectedActions
Related to Rudder - Bug #5389: When two techniques generated with ncf-builder use the same generic method with same parameters, reporting cannot dinstinguish them, and reports "Unknown"ReleasedFrançois ARMANDActions
Has duplicate Rudder - Bug #4674: When modifying a directive based on a meta-technique with multivalued section with same component key, the duplicated component keys are removedReleasedActions

Updated by Nicolas PERRON almost 12 years ago Actions
Copy link
 #1

  • Project changed from 41 to Rudder
  • Category set to Web - Compliance & node report

This is more a Rudder problem than a ncf one.

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

  • Target version changed from 2.11.2 to 2.10.4

Metadata.xml and expected reports are correct, something inside Rudder must fail.
I guess this should happen on Rudder 2.10 also

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #3

  • Status changed from New to Pending technical review
  • Assignee set to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/591

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #4

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

Updated by Matthieu CERDA almost 12 years ago Actions
Copy link
 #6

  • Status changed from Pending release 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
Copy link

Also available in: PDF Atom