Bug #10773
closedRounding error in compliance bar can hide error with very small percent
Description
As reported in #10761, depending of the numbers, we may display percents that don't sum-up to 100% in the compliance bar.
A part of the ticket is to establish a definitive algo about how the computing of such rounding is done (up or down? Always 100 (yes)? Favors error or success?)
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.3 to 4.1.4
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.4 to 4.1.5
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.1.5 to 4.1.6
Updated by Benoît PECCATTE over 7 years ago
- Sort values from small to big
- Have a counter for the rounding error (= displayed value - real value)
- All values <1% are displayed <1% and counted as 1%
- For each other value, round depending on the counter (above i negative, below if positive)
> this should be as close to 100% as possible, more or less 1% (except if there are too many <1%> some value are not rounded to the closest
- Idem except:
- Round to the closest all values interdependently of the counter except the last one
- Substract the counter from the last value before rounding
> This can make sure we hit 100%> only the biggest value is imprecise
Updated by Raphael GAUTHIER over 7 years ago
- Effort required set to Medium
- Priority changed from 50 to 33
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.6 to 4.1.7
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.7 to 4.1.8
- Priority changed from 33 to 32
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.8 to 4.1.9
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.9 to 4.1.10
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 31 to 29
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Alexis Mousset over 6 years ago
- Severity changed from Minor - inconvenience | misleading | easy workaround to Critical - prevents main use of Rudder | no workaround | data loss | security
- Priority changed from 29 to 64
It happens event in nodes list, and even in rules overview in node compliance. We need to go to component level to see errors.
This may hide any configuration issue, and gives a false sense on compliance. Setting to critical.
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.13 to 411
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 411 to 4.1.13
Updated by François ARMAND over 6 years ago
- Related to Bug #12643: Compliance bar appears partially white in some graphes added
Updated by Vincent MEMBRÉ over 6 years ago
I tested really small status (1 error for 1k reports to 1billion)
1k to 20k => Ok! (a small portion appear containing the error)
20k to 21M => 100% green (no error section)
21M and above => Overflow !
Updated by Vincent MEMBRÉ over 6 years ago
Above 20k reports, this breaks because we have less that 0,005 % and since we round to 2 digits, it's rounded to 0,00%
Updated by Benoît PECCATTE over 6 years ago
- User visibility changed from Getting started - demo | first install | level 1 Techniques to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 64 to 49
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.16 to 4.1.17
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 49 to 0
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.18 to 4.1.19
Updated by Alexis Mousset almost 6 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND almost 6 years ago
- Translation missing: en.field_tag_list set to Sponsored
- User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 76
Updated by François ARMAND almost 6 years ago
This is causing grave problem in the case where one among a big number of reports are in error, and that component is critical.
Updated by François ARMAND almost 6 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by Vincent MEMBRÉ almost 6 years ago
- Assignee changed from François ARMAND to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2130
Updated by Rudder Quality Assistant almost 6 years ago
- Assignee changed from François ARMAND to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ almost 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|50e68a2d8bf28efb5e9009965afa87b6bd4eddec.
Updated by François ARMAND almost 6 years ago
- Subject changed from Rounding error in compliance bar to Rounding error in compliance bar can hide error with very small percent
Updated by François ARMAND almost 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.20, 4.3.10 and 5.0.6 which were released today.
Updated by François ARMAND almost 4 years ago
- Related to Bug #18912: White empty segment in compliance bar due to computation bug added
Updated by Nicolas CHARLES almost 3 years ago
- Related to Bug #20373: compliance from API doesn't always adds up to 100% added