Bug #14918
closed
Policy generation fails with if update of dynamic groups takes more than 10 seconds
Added by Nicolas CHARLES over 5 years ago.
Updated over 5 years ago.
Category:
Web - Config management
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
Description
In #14758, we introduced a check at policy generation start that validate all dynamic groups
The timeout was an optimistic 10 seconds, and a user reported more than 3 minutes for dynamic group update (1000 node, 300 groups)
- Related to Bug #14758: Accepting a change request on dynamic group, make the group empty leads an invalid policy generation added
So, we are going to remove the timeout since it can totally break a generation. We prefer to have a never ending policy generation than failing because the groupe generation is long for some reason.
- Status changed from New to In progress
- Assignee set to François ARMAND
- 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/2226
- Assignee changed from Nicolas CHARLES to François ARMAND
- Status changed from Pending technical review to Pending release
- Subject changed from "Dynamic group update time-outed (waited for 10 secondes to finish)" to Policy generation fails with if update of dynamic groups takes more than 10 seconds
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.23, 4.3.13 and 5.0.11 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by