Project

General

Profile

Actions

Bug #25822

closed

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

Added by Clark ANDRIANASOLO 16 days ago. Updated 14 days ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
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:
78
Name check:
To do
Fix check:
Checked
Regression:
No

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 open1 closed)

Related to Rudder - Bug #25332: When changing node properties the old table is sometimes still displayedReleasedFrançois ARMANDActions
Actions

Also available in: Atom PDF