Bug #25617
open
Discordance on node compliance between two tabs
Added by Lucas FRANCOIS 3 months ago.
Updated 9 days ago.
Severity:
Trivial - no functional impact | cosmetic
Description
When in nodes tab it shows 100% of compliance, but when clicking on the node it now shows 99%.
Files
- Priority changed from N/A to To review
- Assignee set to Raphael GAUTHIER
- Priority changed from To review to 2
- 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.
the compliance does not sum up to 100 on the nodes page
- Status changed from New to In progress
- Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER
- Status changed from In progress to New
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Target version changed from 8.1.8 to 8.1.9
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)
- Target version changed from 8.1.9 to 8.1.10
- Target version changed from 8.1.10 to 8.1.11
- Status changed from New to In progress
- 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
- Status changed from Pending technical review to Pending release
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous