Actions
Bug #25332
closed
When changing node properties the old table is sometimes still displayed
Pull Request:
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.
Updated by Vincent MEMBRÉ 7 months ago
- Target version changed from 8.2.0~beta1 to 8.2.0~rc1
- Priority changed from 37 to 74
Updated by Clark ANDRIANASOLO 6 months ago
- Related to Bug #25528: List node with properties inheritance error in status bar for generation added
Updated by Clark ANDRIANASOLO 6 months 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/5920
Updated by Clark ANDRIANASOLO 6 months ago
- Status changed from Pending technical review to Pending release
Updated by François ARMAND 6 months ago
- Has duplicate Bug #25540: Node properties tab : modified values are not displayed until page refresh added
Updated by Vincent MEMBRÉ 6 months ago
- Status changed from Pending release to Released
- Priority changed from 74 to 73
Updated by Clark ANDRIANASOLO 5 months ago
- Related to Bug #25822: Properties on newly created group are not initialized until policy generation or other group properties update added
Actions