Actions
Bug #25617
openDiscordance on node compliance between two tabs
Status:
Pending release
Priority:
2
Assignee:
Category:
Web - UI & UX
Target version:
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
When in nodes tab it shows 100% of compliance, but when clicking on the node it now shows 99%.
Files
Updated by François ARMAND 2 months ago
- Assignee set to Raphael GAUTHIER
- Priority changed from To review to 2
Updated by François ARMAND 2 months ago
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
It seems that the compliance score is not using the specified algo to compute compliance, which leads to rounding errors.
Updated by Nicolas CHARLES 2 months ago
the compliance does not sum up to 100 on the nodes page
Updated by Raphael GAUTHIER about 2 months ago
- Status changed from New to In progress
- Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER
Updated by Raphael GAUTHIER about 2 months ago
- Status changed from In progress to New
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 1 month ago
- Target version changed from 8.1.8 to 8.1.9
Updated by François ARMAND about 1 month ago
On this one, we must understand why it was not caught by our unit tests and if it really use the algo that we have decided. @Vincent MEMBRÉ, can you:
- understand why we fall on that again,
- add the missing unit tests if some are missing (either in elm or scala),
- normalize the computation of percents so that we only have one way to do it (and same algo in scala, in elm)
Updated by Vincent MEMBRÉ 23 days ago
- Target version changed from 8.1.9 to 8.1.10
Updated by Vincent MEMBRÉ 19 days ago
- Target version changed from 8.1.10 to 8.1.11
Updated by Vincent MEMBRÉ 9 days ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER
- Pull Request set to https://github.com/Normation/rudder/pull/6081
Updated by Anonymous 8 days ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|b83adb20f2141e9aa48a371e0748792af2e73422.
Actions