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
Added by Nicolas CHARLES over 5 years ago.
Updated over 5 years ago.
Category:
Web - Config management
Description
Parent ticket create the generation to continue if there were any differences
this is a huge behavioural change, and should be optional
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- 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
- Status changed from Pending technical review to Discussion
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Status changed from Discussion to Pending technical review
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Name check changed from To do to Reviewed
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.12 which was released today.
Also available in: Atom
PDF