Project

General

Profile

Actions

Bug #25533

closed

Group properties inheritance issue : Property modified for a group do not appear changed if another group defines the same property for one node both have in common.

Added by Michel BOUISSOU about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
-
Target version:
Severity:
UX impact:
I hate Rudder for that
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

Observed behaviour :

- Group A and group B contain the same node.
- Group A and group B define the same JSON property at group level, with the same value.

- Changing the property value in group A produces no visible error, but on the group page, the property doesn't seem to have been updated at all.

- Removing the property in group A correctly shows the property now absent on the group page.

- Recreating the property on group A produces no visible error, but on the group page, the property doesn't seem to have been created. it is absent.

  • Then *

- Updating group B criteria so it doesn't contain the same nodes as group A anymore, causes the property that was recreated on group A to suddenly appear on group A's page.

The webaapp log show no information that could relate to this.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #25528: List node with properties inheritance error in status bar for generationReleasedFrançois ARMANDActions
Actions #1

Updated by Michel BOUISSOU about 2 months ago

  • Related to Bug #25528: List node with properties inheritance error in status bar for generation added
Actions #2

Updated by Clark ANDRIANASOLO about 2 months ago

  • Target version set to 8.2.0~rc1

Related to issue #25528, the logs are in fact swallowed somewhere during deployment when attempting to merge the node hierarchy of properties for all nodes.

Also when the property cannot be resolved the cache of properties in 8.2 seems to be updated with an empty list of properties for the node so the property is simply not added to the node

Actions #3

Updated by François ARMAND about 1 month ago

  • Status changed from New to Resolved

Resolved by #25528

Actions

Also available in: Atom PDF