Actions
Bug #15078
closed
Bug #14465: Generation fails with "Task FutureTask rejected from ThreadPoolExecutor" due to timeout in JS computation
Add an option to fail or not during policy generation if NodeConfigurations cannot be created
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
Parent ticket create the generation to continue if there were any differences
this is a huge behavioural change, and should be optional
Updated by Nicolas CHARLES over 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2264
Updated by Rudder Quality Assistant over 5 years ago
- Status changed from Pending technical review to Discussion
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Discussion to Pending technical review
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
Updated by Rudder Quality Assistant over 5 years ago
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|ad4f3bf0d28323904244af8634d6f6e87e290600.
Updated by François ARMAND over 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset over 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.12 which was released today.
Actions