Project

General

Profile

Actions

Bug #7103

closed

When we have node in no answer/pending, with a directive acting several time on the same object, the compliance % is invalid

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 by Nicolas CHARLES over 10 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

If I configure a file edition directive, to edit twice the same file, and apply it to a bug of node, the compliance % will be invalid as it will consider 1 pending reports for all node that did not answer, and 2 reports per node that answer; resulting in a much optimistic result

In this example, I have 4 nodes, only one replied
I would have expected 25% (bottom) rather than 40% (top: 2 success out of 2 success + 4 no answer)


Files

compliance-unexpected.png (52.2 KB) compliance-unexpected.png unexpected ocmpliance Nicolas CHARLES, 2015-08-13 16:47
compliance-ok.png (78.4 KB) compliance-ok.png 2.11.12~rc1~git201507050323 Nicolas CHARLES, 2015-08-13 16:49
compliance-unexpected.png
compliance-ok.png

Related issues 2 (0 open2 closed)

Related to Rudder - Bug #7037: Reporting cannot be used when there is several component with the same value and several messages ReleasedFrançois ARMANDActions
Related to Rudder - Bug #6846: Reporting is not ok when we must receive multiple reportsRejectedActions

Updated by Nicolas CHARLES over 10 years ago Actions #1

  • Related to Bug #7037: Reporting cannot be used when there is several component with the same value and several messages added

Updated by Nicolas CHARLES over 10 years ago Actions #2

compliance-ok.png

this was introduced by #7037 and associated

here, a 2.11.12 doesn't exhibit this behaviour

Updated by Vincent MEMBRÉ about 10 years ago Actions #3

  • Target version changed from 2.10.17 to 2.10.18

Updated by Vincent MEMBRÉ about 10 years ago Actions #4

  • Target version changed from 2.10.18 to 2.10.19

Updated by Vincent MEMBRÉ about 10 years ago Actions #5

  • Target version changed from 2.10.19 to 2.10.20

Updated by Vincent MEMBRÉ almost 10 years ago Actions #6

  • Target version changed from 2.10.20 to 277

Updated by Vincent MEMBRÉ almost 10 years ago Actions #7

  • Target version changed from 277 to 2.11.18

Updated by Vincent MEMBRÉ almost 10 years ago Actions #8

  • Target version changed from 2.11.18 to 2.11.19

Updated by Vincent MEMBRÉ over 9 years ago Actions #9

  • Target version changed from 2.11.19 to 2.11.20

Updated by Vincent MEMBRÉ over 9 years ago Actions #10

  • Target version changed from 2.11.20 to 2.11.21

Updated by Vincent MEMBRÉ over 9 years ago Actions #11

  • Target version changed from 2.11.21 to 2.11.22

Updated by Vincent MEMBRÉ over 9 years ago Actions #12

  • Target version changed from 2.11.22 to 2.11.23

Updated by Vincent MEMBRÉ over 9 years ago Actions #13

  • Target version changed from 2.11.23 to 2.11.24

Updated by Vincent MEMBRÉ about 9 years ago Actions #14

  • Target version changed from 2.11.24 to 308

Updated by Vincent MEMBRÉ about 9 years ago Actions #15

  • Target version changed from 308 to 3.1.14

Updated by Vincent MEMBRÉ about 9 years ago Actions #16

  • Target version changed from 3.1.14 to 3.1.15

Updated by Vincent MEMBRÉ about 9 years ago Actions #17

  • Target version changed from 3.1.15 to 3.1.16

Updated by Vincent MEMBRÉ about 9 years ago Actions #18

  • Target version changed from 3.1.16 to 3.1.17

Updated by Vincent MEMBRÉ almost 9 years ago Actions #19

  • Target version changed from 3.1.17 to 3.1.18

Updated by Vincent MEMBRÉ over 8 years ago Actions #20

  • Target version changed from 3.1.18 to 3.1.19

Updated by Jonathan CLARKE over 8 years ago Actions #21

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 30

Updated by Jonathan CLARKE over 8 years ago Actions #22

  • Related to Bug #6846: Reporting is not ok when we must receive multiple reports added

Updated by Jonathan CLARKE over 8 years ago Actions #23

Is this the same as #6846?

Updated by Vincent MEMBRÉ over 8 years ago Actions #24

  • Target version changed from 3.1.19 to 3.1.20

Updated by Vincent MEMBRÉ over 8 years ago Actions #25

  • Target version changed from 3.1.20 to 3.1.21

Updated by Vincent MEMBRÉ over 8 years ago Actions #26

  • Target version changed from 3.1.21 to 3.1.22

Updated by Benoît PECCATTE over 8 years ago Actions #27

  • Priority changed from 30 to 43

Updated by Vincent MEMBRÉ over 8 years ago Actions #28

  • Target version changed from 3.1.22 to 3.1.23

Updated by Vincent MEMBRÉ about 8 years ago Actions #29

  • Target version changed from 3.1.23 to 3.1.24

Updated by Vincent MEMBRÉ about 8 years ago Actions #30

  • Target version changed from 3.1.24 to 3.1.25

Updated by Vincent MEMBRÉ almost 8 years ago Actions #31

  • Target version changed from 3.1.25 to 387

Updated by Vincent MEMBRÉ almost 8 years ago Actions #32

  • Target version changed from 387 to 4.1.10

Updated by Vincent MEMBRÉ over 7 years ago Actions #33

  • Target version changed from 4.1.10 to 4.1.11

Updated by Vincent MEMBRÉ over 7 years ago Actions #34

  • Target version changed from 4.1.11 to 4.1.12

Updated by Vincent MEMBRÉ over 7 years ago Actions #35

  • Target version changed from 4.1.12 to 4.1.13

Updated by Vincent MEMBRÉ over 7 years ago Actions #36

  • Target version changed from 4.1.13 to 4.1.14

Updated by Benoît PECCATTE over 7 years ago Actions #37

  • Target version changed from 4.1.14 to 4.1.15

Updated by Vincent MEMBRÉ about 7 years ago Actions #38

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 43 to 44

Updated by Vincent MEMBRÉ about 7 years ago Actions #39

  • Target version changed from 4.1.16 to 4.1.17

Updated by François ARMAND about 7 years ago Actions #40

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

Compliance calcul changed a lot since rudder 2.10. This is not happening anymore.

Actions

Also available in: PDF Atom