Bug #25822: Properties on newly created group are not initialized until policy generation or other group properties update - Rudder - Issue Tracker

Actions

Copy link

Bug #25822

closed

Properties on newly created group are not initialized until policy generation or other group properties update

Added by Clark ANDRIANASOLO about 2 months ago. Updated about 1 month ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - UI & UX

Target version:

8.2.1

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

It bothers me each time

User visibility:

Getting started - demo | first install | Technique editor and level 1 Techniques

Effort required:

Small

Priority:

Name check:

To do

Fix check:

Checked

Regression:

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.

Related issues 1 (0 open — 1 closed)