Project

General

Profile

Actions
Copy link

User story #25383

closed

Worst report takes the worst component instead of block

Added by Clark ANDRIANASOLO 4 months ago. Updated 2 months ago.

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
8.2.0~rc1
Pull Request:
https://github.com/Normation/rudder/p...
UX impact:
It bothers me each time
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Name check:
To do
Fix check:
To do
Regression:
No

Description

In the following scenario of reporting with the "worst" reporting logic, the root block result is surprising : 

block1 : worst => 0% error
  - block11: weighted => 33% error
     - gm1: 0%
     - gm2: 100%
     - gm3: 100%
  - block12: weighted => 100% success
     - gm4: 100%
     - gm5: 100%

We expect a worst of 33%, as if the block11 itself is the worst component

UPDATE: we need a new reporting logic kind, because both make sense in different contexte (the other one when we base our logic on the compliance level structure, not the percent). I'm updating the type of tracker accordingly.

Subtasks 2 (0 open — 2 closed)

User story #25600: Compliance reporting with type worst-case-percent is not known by ruddercReleasedAlexis MoussetActions
User story #25604: Reporting type should be focus-worst instead of worst-case-percentReleasedFrançois ARMANDActions

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #25513: worst report by percentage seems to be non fonctionnalReleasedFrançois ARMANDActions
Has duplicate Rudder - Architecture #25385: We need a reportingLogic computing on percentRejectedActions
Actions
Copy link
 #1

Updated by Clark ANDRIANASOLO 4 months ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by Clark ANDRIANASOLO 4 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/5846
Actions
Copy link
 #3

Updated by Clark ANDRIANASOLO 4 months ago

Actions
Copy link
 #4

Updated by Clark ANDRIANASOLO 4 months ago

  • Target version changed from 8.1.7 to 8.2.0~beta1
  • Priority changed from 60 to 30

This is targeting 8.2 because of techniques compatibility issues that could be introduced by adding a new type of reporting logic in 8.1

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.2.0~beta1 to 8.2.0~rc1
  • Priority changed from 30 to 60
Actions
Copy link
 #6

Updated by François ARMAND 4 months ago

Actions
Copy link
 #7

Updated by François ARMAND 4 months ago

Actions
Copy link
 #8

Updated by François ARMAND 4 months ago

  • Tracker changed from Bug to User story
  • Description updated (diff)
  • Severity deleted (Minor - inconvenience | misleading | easy workaround)
  • Priority deleted (60)
Actions
Copy link
 #9

Updated by Clark ANDRIANASOLO 3 months ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #10

Updated by François ARMAND 3 months ago

  • Priority changed from N/A to 1 (highest)
Actions
Copy link
 #11

Updated by Clark ANDRIANASOLO 3 months ago

  • Subtask #25600 added
Actions
Copy link
 #12

Updated by Clark ANDRIANASOLO 3 months ago

  • Related to Bug #25513: worst report by percentage seems to be non fonctionnal added
Actions
Copy link
 #13

Updated by Clark ANDRIANASOLO 3 months ago

  • Subtask #25604 added
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ 2 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.2.0~rc1 which was released today.

Actions
Copy link

Also available in: Atom PDF