Bug #14758
closed
Accepting a change request on dynamic group, make the group empty leads an invalid policy generation
Added by Nicolas CHARLES almost 5 years ago.
Updated almost 5 years ago.
Category:
Web - Config management
Description
When we accept a change request on a dynamic group, the group is empty, and policies are generated, with no node in this groupe (see screenshot)
we need to wait for the next dynamic group refresh to correct it.
solution is to force dynamic group update during first phase of deploy
Files
2 options:
- extend DynGroupUpdaterService to update all group (this is sync and blocking) - so we know when it's finished. However, if we update all groups during a run of dynamic group update batch, chaos is likely to happen
- trigger a dynamic group update batch, and wait for it to be idel
- 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/2202
pull request fixes the issue, BUT it causes double policy generation (the second not doing anything), as the groups are updated)
- Related to Bug #4480: When restoring archive (full or groups) dynamic groups are created empty added
- Related to Bug #14766: When accepting a change request on a group, it's node list should be computed before saving added
- Related to Architecture #14767: When we accept nodes, dynamic group should be automatically updated at the end of the acceptation, in a synchronized way added
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Status changed from Pending technical review to Pending release
- Subject changed from when accepting a change request on dynamic group, the group is empty, policy generated are so invalid, and it fixes itself only at next dynamic group refresh to Accepting a change request on dynamic group, make the group empty leads an invalid policy generation
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.22, 4.3.12 and 5.0.10 which were released today.
- Related to Bug #14918: Policy generation fails with if update of dynamic groups takes more than 10 seconds added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 