Project

General

Profile

Actions

Bug #6846

closed

Reporting is not ok when we must receive multiple reports

Added by Vincent MEMBRÉ almost 6 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
1
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0

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:
My Rule will tell me that i'm:
  • 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

bug_fucked_reporting.png (297 KB) bug_fucked_reporting.png Vincent MEMBRÉ, 2015-06-26 17:10

Related issues

Related to Rudder - Bug #7103: When we have node in no answer/pending, with a directive acting several time on the same object, the compliance % is invalidRejectedActions
Actions #1

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.0.7 to 3.0.8
Actions #2

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.0.8 to 3.0.9
Actions #3

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.0.9 to 3.0.10
Actions #4

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.0.10 to 3.0.11
Actions #5

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.0.11 to 3.0.12
Actions #6

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.0.12 to 3.0.13
Actions #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.0.13 to 3.0.14
Actions #8

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 3.0.14 to 3.0.15
Actions #9

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 3.0.15 to 3.0.16
Actions #10

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions #11

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.0.17 to 302
Actions #12

Updated by Alexis MOUSSET almost 5 years ago

  • Target version changed from 302 to 3.1.12
Actions #13

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #14

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #15

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #16

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #17

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #18

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #19

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #20

Updated by Jonathan CLARKE about 4 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
Actions #21

Updated by Jonathan CLARKE about 4 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
Actions #22

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #23

Updated by Jonathan CLARKE about 4 years ago

  • Assignee deleted (Vincent MEMBRÉ)
Actions #24

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #25

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #26

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 45 to 58
Actions #27

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #28

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #29

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #30

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.25 to 387
Actions #31

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 387 to 4.1.10
Actions #32

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #33

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #34

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #35

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #36

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 58 to 59
Actions #37

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 59 to 60
Actions #38

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #39

Updated by François ARMAND over 2 years ago

  • Status changed from New to Rejected
  • Priority changed from 60 to 0

The compliance calculus were totaly done a new since Rudder 3.0. This case reports are now OK. Closing that.

Actions

Also available in: Atom PDF