Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem
======================
Colors in result.html don't reflect nature of the result properly:
RESULT || COLOR
||-------.-------
|| bar | box
=================||=======|=======
passed || green | green
fixed || red | green
failed || ??? | red
informational || red | grey
needs_action || red | grey
needs_inspection || red | grey
notapplicable || ??? | grey
error || ??? | red
Legend:
* 'bar' - the colored proportion bar under "Compliance and Scoring"
section
* 'box' - individual result boxes you can see when you click "Show
all result details"
* 'color: ???' - the result is not represented or misrepresented
(e.g. XYZ counted as "passed") in the bar
See attached screenshots and reports for illustration.
Version-Release number of selected component
============================================
preupgrade-assistant-2.1.10-6.el6
How reproducible
================
Always
Steps to Reproduce
==================
1. Run upgrade path with various results
For example, test /CoreOS/preupgrade-assistant/preupg/result-files runs
a fake upgrade path that contains one of each valid results
2. Open result.html
3. Observe result severity color coding
Actual results
==============
Colors and gauges don't match nature of result
* (A) in bar, 'informational' and 'fixed' are red
* (B) in bar, something is misinterpreted as "passed" (there's only one
'passed' in the test but the bar counts 2)
* (C) 'needs_inspection', 'needs_action' and 'informational' boxes
are all grey
* (D) there's also another similar bar called "Severity of failed
rules", which apparently only contains 'failed' statistics, however
it's coded green here.
* (E) 'error' is missing from the bar
* could be more...
Expected results
================
Colors should match nature of result, the report should be intuitive.
For example:
* (A) 'informational' and 'fixed' should have good/neutral color
* (B) only 'passed' should show as 'passed' here
* (C) at leasr 'needs_action' and 'needs_inspection' should not be grey
* (D) hard to say what to expect and whether this bar could make sense
given we have only one "failed" severity type.
* (E) 'error' should not be missing from the bar
Additional info
===============
We're using custom results inherited from original XCCDF results. My first guess is that the definition we give is not complete so these custom results inherit some "default" values inappropriate fot their new meaning, which further messes up the stats and color coding.
Note about attachments:
* "realistic use case" is simple preupg run on a fresh ppc64 install.
* "fake upgrade path" is a mock upgrade path forged to generate each
result type exactly once (a modified version from test mentioned above).
Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.
Description of problem ====================== Colors in result.html don't reflect nature of the result properly: RESULT || COLOR ||-------.------- || bar | box =================||=======|======= passed || green | green fixed || red | green failed || ??? | red informational || red | grey needs_action || red | grey needs_inspection || red | grey notapplicable || ??? | grey error || ??? | red Legend: * 'bar' - the colored proportion bar under "Compliance and Scoring" section * 'box' - individual result boxes you can see when you click "Show all result details" * 'color: ???' - the result is not represented or misrepresented (e.g. XYZ counted as "passed") in the bar See attached screenshots and reports for illustration. Version-Release number of selected component ============================================ preupgrade-assistant-2.1.10-6.el6 How reproducible ================ Always Steps to Reproduce ================== 1. Run upgrade path with various results For example, test /CoreOS/preupgrade-assistant/preupg/result-files runs a fake upgrade path that contains one of each valid results 2. Open result.html 3. Observe result severity color coding Actual results ============== Colors and gauges don't match nature of result * (A) in bar, 'informational' and 'fixed' are red * (B) in bar, something is misinterpreted as "passed" (there's only one 'passed' in the test but the bar counts 2) * (C) 'needs_inspection', 'needs_action' and 'informational' boxes are all grey * (D) there's also another similar bar called "Severity of failed rules", which apparently only contains 'failed' statistics, however it's coded green here. * (E) 'error' is missing from the bar * could be more... Expected results ================ Colors should match nature of result, the report should be intuitive. For example: * (A) 'informational' and 'fixed' should have good/neutral color * (B) only 'passed' should show as 'passed' here * (C) at leasr 'needs_action' and 'needs_inspection' should not be grey * (D) hard to say what to expect and whether this bar could make sense given we have only one "failed" severity type. * (E) 'error' should not be missing from the bar Additional info =============== We're using custom results inherited from original XCCDF results. My first guess is that the definition we give is not complete so these custom results inherit some "default" values inappropriate fot their new meaning, which further messes up the stats and color coding.