Bug #25822
closedProperties on newly created group are not initialized until policy generation or other group properties update
Description
In 8.2 since #25219 we have a cache of properties by node and group, but the cache for group does not contain the new group when it is newly created, so the properties of a group are not found when displaying them on the UI. In general, the group properties are not resolved yet, unless any property is changed in any other group or node, which triggers the computation and resolution of properties of all groups (also doing a manual generation of policy helps).
We need to initialize any newly created group with its resolved properties within the properties cache.
The issue concerns both group creation from API and from the Rudder UI, so both use cases need to be addressed.
Updated by Clark ANDRIANASOLO 30 days ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 30 days ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5997
Updated by Clark ANDRIANASOLO 30 days ago
- Related to Bug #25332: When changing node properties the old table is sometimes still displayed added
Updated by Clark ANDRIANASOLO 29 days ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|95bdf46064c8580ef68397b813b1752bd052428b.
Updated by Vincent MEMBRÉ 28 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.1 which was released today.