Actions
Bug #6846
closedReporting is not ok when we must receive multiple reports
Status:
Rejected
Priority:
1 (highest)
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Let say i'm using a technique that needs two reports to be complete on a same component value (like distribute key ssh, using the same tag on different user)
If my nodes are working great and the correct reports yay it's fine!
But if one of them is off, or a reporting is missing, my reporitng compliance will not be ok :
applying/No report/ missing will always count as one report, but other state will count as many report as received (if i receive 3 reports it will count for 3)
Example:
I have 3 Nodes that should send me three reports:- N1 is off,
- N2 is in success but only sending two reports
- N3 is in erreor and send all reports:
- 17% No report (1/6)
- 33% Success (2/6)
- 50% error (3/6)
But if i look at my node details:
I will have- N1 100% No report
- N2 100% success
- N3 100% Error
The rule shoudl be instead (33% no report, 33% error, 23% success, 11% missing (the missing success)
I'm adding a screen of a look alike case
Files
Updated by Jonathan CLARKE about 8 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Priority set to 45
Updated by Jonathan CLARKE about 8 years ago
- Related to Bug #7103: When we have node in no answer/pending, with a directive acting several time on the same object, the compliance % is invalid added
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
- Priority changed from 58 to 59
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.15 to 4.1.16
- Priority changed from 59 to 60
Updated by François ARMAND over 6 years ago
- Status changed from New to Rejected
- Priority changed from 60 to 0
Actions