Actions
Bug #10908
closedWhen hooks in policy-generation-node-ready or policy-generation-node-finished fails, there is no error in the generation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Error codes of hooks in policy-generation-node-ready or policy-generation-node-finished are not handled: if we return 1, it happily continues generation and finishes
It seems it's because return code is encapsulated in a Full - so it's always ok
So there is no real check on policy generation validity
Updated by François ARMAND over 7 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1664
Updated by François ARMAND over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d180e309ac8cb321bfedb34d9f0a72c482c00071.
Updated by Alexis Mousset over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.4 which was not released (see changelog for details), and is available in Rudder 4.1.5.
- 4.1.5: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions