Project

General

Profile

Actions

Bug #6163

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"

The generated promises are invalid when there are no ncf techniques

Added by Nicolas CHARLES almost 10 years ago. Updated over 9 years ago.

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

Description

In #5389, we changed the way the bundlesequence is written
Unfortunately, if there are no ncf techniques to apply, we have a syntax error (extra , in the bundlesequence)

Actions #1

Updated by Nicolas CHARLES almost 10 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/68
Actions #2

Updated by Nicolas CHARLES almost 10 years ago

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

Applied in changeset clerk:commit:95efa40dd508d448226bc2c33aba073aefeb74d0.

Actions #3

Updated by François ARMAND almost 10 years ago

Applied in changeset clerk:commit:6afd28b2c3c7a12f5e6ff413cdc03e8ab3c4251d.

Actions #4

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions #5

Updated by Vincent MEMBRÉ almost 10 years ago

  • Parent task set to #5389
Actions #6

Updated by Vincent MEMBRÉ almost 10 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 #7

Updated by Benoît PECCATTE over 9 years ago

  • Category changed from 14 to Web - Config management
Actions

Also available in: Atom PDF