Project

General

Profile

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 about 3 years ago. Updated about 2 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Target version (plugin):
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Pull Request:
Priority:
43

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)

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
938
939

Related issues

Related to Rudder - Bug #7037: Reporting cannot be used when there is several component with the same value and several messages Released2015-07-30
Related to Rudder - Bug #6846: Reporting is not ok when we must receive multiple reportsNew

History

#1 Updated by Nicolas CHARLES about 3 years ago

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

#2 Updated by Nicolas CHARLES about 3 years ago

939

this was introduced by #7037 and associated

here, a 2.11.12 doesn't exhibit this behaviour

#3 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.10.17 to 2.10.18

#4 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.10.18 to 2.10.19

#5 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.10.19 to 2.10.20

#6 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.10.20 to 277

#7 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 277 to 2.11.18

#8 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.18 to 2.11.19

#9 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.19 to 2.11.20

#10 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.20 to 2.11.21

#11 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.21 to 2.11.22

#12 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.22 to 2.11.23

#13 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#14 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.24 to 308

#15 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 308 to 3.1.14

#16 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.14 to 3.1.15

#17 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.15 to 3.1.16

#18 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.16 to 3.1.17

#19 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.17 to 3.1.18

#20 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.18 to 3.1.19

#21 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 Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 30

#22 Updated by Jonathan CLARKE over 1 year ago

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

#23 Updated by Jonathan CLARKE over 1 year ago

Is this the same as #6846?

#24 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.19 to 3.1.20

#25 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#26 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#27 Updated by Benoît PECCATTE about 1 year ago

  • Priority changed from 30 to 43

#28 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.22 to 3.1.23

#29 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.23 to 3.1.24

#30 Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 3.1.24 to 3.1.25

#31 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 3.1.25 to 387

#32 Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 387 to 4.1.10

#33 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.10 to 4.1.11

#34 Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 4.1.11 to 4.1.12

#35 Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 4.1.12 to 4.1.13

#36 Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 4.1.13 to 4.1.14

#37 Updated by Benoît PECCATTE about 2 months ago

  • Target version changed from 4.1.14 to 4.1.15

Also available in: Atom PDF