Project

General

Profile

Actions

Bug #25332

closed

When changing node properties the old table is sometimes still displayed

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

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
It bothers me each time
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
73
Name check:
To do
Fix check:
To do
Regression:
No

Description

When adding or editing a node property, a success notification is shown and the property is actually updated on the API, but the table can remain to its old state : without the property in case of adding one, or with the previous property value in case of editing one.

It seems to happen to me only on a local test environment, and with "No throttling" enabled on the browser. When I enable throttling with "GPRS", the problem does not occurs.
There seems to be a race condition in updating the state of the table and refreshing properties.
A workaround is to refresh the table from the refresh button.

It seems to happen only on my 8.2 instance and I could not reproduce on a 8.1 instance.


Related issues 3 (0 open3 closed)

Related to Rudder - Bug #25528: List node with properties inheritance error in status bar for generationReleasedFrançois ARMANDActions
Related to Rudder - Bug #25822: Properties on newly created group are not initialized until policy generation or other group properties updateReleasedFrançois ARMANDActions
Has duplicate Rudder - Bug #25540: Node properties tab : modified values are not displayed until page refreshResolvedActions
Actions

Also available in: Atom PDF