Actions
Bug #25513
closedworst report by percentage seems to be non fonctionnal
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
I have a block one with 2 subblocks (two and three), and worst report by percentage
reporting on "two" is normal, with 25% compliance (3 errors and one repairs), and on "three" is is also worst report by compliance percentage
Block 3 has 4 methods command execution which are the same as in block "two" (literraly the same content)
As a result, block "two" has 25% compliance, block "three" has 0% compliance
and block "one" has 25% compliance. I would have expected 0%
here is the detailed reporting
Files
Updated by Clark ANDRIANASOLO about 2 months ago
- Status changed from New to In progress
- Assignee set to Clark ANDRIANASOLO
Updated by Clark ANDRIANASOLO about 2 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/5913
Updated by Clark ANDRIANASOLO about 2 months ago
- Related to User story #25383: Worst report takes the worst component instead of block added
Updated by Clark ANDRIANASOLO about 2 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|c7f3744f0a218cad4ffe796dd11bf52eb9f87a7c.
Updated by Vincent MEMBRÉ about 1 month ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~rc1 which was released today.
Actions