Project

General

Profile

Bug #6846

Reporting is not ok when we must receive multiple reports

Added by Vincent MEMBRÉ over 3 years ago. Updated 29 days ago.

Status:
Rejected
Priority:
1
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Pull Request:
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

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

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 invalidRejected

History

#1 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.0.7 to 3.0.8

#2 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.0.8 to 3.0.9

#3 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 3.0.9 to 3.0.10

#4 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 3.0.10 to 3.0.11

#5 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 3.0.11 to 3.0.12

#6 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 3.0.12 to 3.0.13

#7 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.0.13 to 3.0.14

#8 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.0.14 to 3.0.15

#9 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.0.15 to 3.0.16

#10 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.0.16 to 3.0.17

#11 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.0.17 to 302

#12 Updated by Alexis MOUSSET over 2 years ago

  • Target version changed from 302 to 3.1.12

#13 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.12 to 3.1.13

#14 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.13 to 3.1.14

#15 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.14 to 3.1.15

#16 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.15 to 3.1.16

#17 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.16 to 3.1.17

#18 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.17 to 3.1.18

#19 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.18 to 3.1.19

#20 Updated by Jonathan CLARKE over 1 year 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

#21 Updated by Jonathan CLARKE over 1 year 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

#22 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.19 to 3.1.20

#23 Updated by Jonathan CLARKE over 1 year ago

  • Assignee deleted (Vincent MEMBRÉ)

#24 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#25 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#26 Updated by Benoît PECCATTE over 1 year ago

  • Priority changed from 45 to 58

#27 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.22 to 3.1.23

#28 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.23 to 3.1.24

#29 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.24 to 3.1.25

#30 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.25 to 387

#31 Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 387 to 4.1.10

#32 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 4.1.10 to 4.1.11

#33 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.11 to 4.1.12

#34 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.12 to 4.1.13

#35 Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 4.1.13 to 4.1.14

#36 Updated by Benoît PECCATTE 4 months ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 58 to 59

#37 Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 59 to 60

#38 Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 4.1.16 to 4.1.17

#39 Updated by François ARMAND 29 days 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.

Also available in: Atom PDF