Project

General

Profile

Actions

Bug #6171

closed

Bug #5389: When two techniques generated with ncf-builder use the same generic method with same parameters, reporting cannot dinstinguish them, and reports "Unknown"

There are no Not applicable reports anymore with ncf technique

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

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Following the change in the parent ticket, ncf doesn't report anymore Not Applicable because the bundlesequence is invalid

Actions #1

Updated by Nicolas CHARLES about 9 years ago

  • Category set to Web - Compliance & node report

The issue is that we define a wrong technique name before calling the bundle that make the reports for NA component

Actions #2

Updated by Nicolas CHARLES about 9 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/cf-clerk/pull/69
Actions #3

Updated by Nicolas CHARLES about 9 years ago

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

Applied in changeset clerk:commit:b784b9b08e04083214e875d12deb7973e693f120.

Actions #4

Updated by François ARMAND about 9 years ago

Applied in changeset clerk:commit:cc70469f1b3ba9e0182cee69afe7445df6654933.

Actions #5

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions #6

Updated by Vincent MEMBRÉ about 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.10 and 2.11.7, which were these days.

Actions

Also available in: Atom PDF