Rudder

So, it's less trivial than initially thought:

- 1/ updating dynamic group is done asynchronously, so if we start it before starting promise generation, the result will certainly not be what we want (only partial update of groups ?)
- 2/ but if we issue a not asynchronous dynamic update, it may be long and make the import process even longer.

So, it seems that we want a way to start other things at the end of the dyngroup generation, something "on complete" (that does not exists for now).

Targeting to 5.0, as #14758 take care of the workaround in 4.1

when importing an archive, it should compute node list before saving. This should be synchronized, as others actions can happen at the same time (accept node, change request, etc), and this computation should block loading nodes list in policy generation

PR https://github.com/Normation/rudder/pull/2204

Applied in changeset rudder|6b7a91211ab4eea09f2e3e5b0d9f1027d4ac80b8.

This bug has been fixed in Rudder 4.1.22, 4.3.12 and 5.0.10 which were released today.

• 4.1.22 changelog
• 4.3.12 changelog
• 5.0.10 changelog
• Upgrade manual