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
Status:
Released
Priority:
1
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
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)
Updated by Nicolas CHARLES over 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/68
Updated by Nicolas CHARLES over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset clerk:commit:95efa40dd508d448226bc2c33aba073aefeb74d0.
Updated by François ARMAND over 9 years ago
Applied in changeset clerk:commit:6afd28b2c3c7a12f5e6ff413cdc03e8ab3c4251d.
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.9 to 2.10.10
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.
- Announcement 2.10 2.11
- Changelog 2.10 2.11
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE about 9 years ago
- Category changed from 14 to Web - Config management
Actions