Project

General

Profile

Actions

Bug #25617

open

Discordance on node compliance between two tabs

Added by Lucas FRANCOIS 11 months ago. Updated 1 day ago.

Status:
New
Priority:
2
Category:
Web - UI & UX
Target version:
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

Actions #1

Updated by Lucas FRANCOIS 11 months ago

  • Priority changed from N/A to To review
Actions #2

Updated by François ARMAND 11 months ago

  • Assignee set to Raphael GAUTHIER
  • Priority changed from To review to 2
Actions #3

Updated by François ARMAND 11 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.

Actions #4

Updated by Nicolas CHARLES 11 months ago

the compliance does not sum up to 100 on the nodes page

Actions #5

Updated by Raphael GAUTHIER 11 months ago

  • Status changed from New to In progress
  • Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER
Actions #6

Updated by Raphael GAUTHIER 11 months ago

  • Status changed from In progress to New
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
Actions #7

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 8.1.8 to 8.1.9
Actions #8

Updated by François ARMAND 10 months 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)

Actions #9

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 8.1.9 to 8.1.10
Actions #10

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 8.1.10 to 8.1.11
Actions #11

Updated by Vincent MEMBRÉ 9 months ago

  • Status changed from New to In progress
Actions #12

Updated by Vincent MEMBRÉ 9 months 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
Actions #13

Updated by Anonymous 9 months ago

  • Status changed from Pending technical review to Pending release
Actions #14

Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from Pending release to New

Reverted because it removed the way to show compliance percent

Actions #15

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 8.1.11 to 8.1.12
Actions #16

Updated by Alexis Mousset 7 months ago

  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
Actions #17

Updated by Alexis Mousset 7 months ago

  • Target version changed from 8.1.12 to 8.2.5
Actions #18

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 8.2.5 to 8.2.6
Actions #19

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.2.6 to 8.2.7
Actions #20

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.2.7 to 8.2.8
Actions #21

Updated by Félix DALLIDET 2 months ago

  • Target version changed from 8.2.8 to 8.2.9
Actions #22

Updated by Vincent MEMBRÉ 1 day ago

  • Target version changed from 8.2.9 to 8.2.10
Actions

Also available in: Atom PDF