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

Added by Nicolas CHARLES over 8 years ago. Updated over 5 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

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 ARMAND2015-07-30Actions
Related to Rudder - Bug #6846: Reporting is not ok when we must receive multiple reportsRejectedActions
Actions #1

Updated by Nicolas CHARLES over 8 years ago

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

Updated by Nicolas CHARLES over 8 years ago

this was introduced by #7037 and associated

here, a 2.11.12 doesn't exhibit this behaviour

Actions #3

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions #5

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions #6

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.20 to 277
Actions #7

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 277 to 2.11.18
Actions #8

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #9

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #10

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #11

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #12

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #13

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #14

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions #15

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions #16

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #17

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #18

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #19

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #20

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #21

Updated by Jonathan CLARKE about 7 years ago

  • 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
Actions #22

Updated by Jonathan CLARKE about 7 years ago

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

Updated by Jonathan CLARKE about 7 years ago

Is this the same as #6846?

Actions #24

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #25

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #26

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #27

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 30 to 43
Actions #28

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #29

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #30

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #31

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.25 to 387
Actions #32

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 387 to 4.1.10
Actions #33

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #34

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #35

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #36

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #37

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #38

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 43 to 44
Actions #39

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #40

Updated by François ARMAND over 5 years ago

  • 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: Atom PDF