Bug 2162882

Summary: [RFE] Introduce human readable form for Host - Statuses report template
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: ReportingAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: David Moore <damoore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: damoore, dsinglet, iballou, rgreene, vsedmik, zhunting
Target Milestone: 6.15.0Keywords: FutureFeature, Reopened, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-23 17:13:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2023-01-21 19:39:34 UTC
Description of problem:
In the report template page, insert a new column with a description of each report. There are some reports that are clear to understand. However, let's use this as example, "Host - Statuses" and the results will be something as below.
---
Name,Global,Addons,Build,Compliance,Configuration,Errata,Execution,Insights,Inventory,OVAL scan,Role,Service level,Subscription,System purpose,Traces,Usage
wallsat612-rhel8.d.sysmgmt.cee.redhat.com,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
---

So, it's not clear what expect for them, like a matrix. Should it be 0 for absent and 1 for present?

When checking for the method (all_host_statuses_hash) in About - DSL template page, we can see as below
---
all_host_statuses(@host) # => {"Addons"=>0, "Build"=>1, "Compliance"=>0, "Configuration"=>0, "Errata"=>0, "Execution"=>1, "Role"=>0, "Service Level"=>0, "Subscription"=>0, "System Purpose"=>0, "Traces"=>0, "Usage"=>0}
---

But again, it's not clear to the customer what this means.

Version-Release number of selected component (if applicable):
6.12

How reproducible:
100%

Steps to Reproduce:
1. Generate the report (Hosts - Statuses)
2. 
3.

Actual results:
The CSV that we don't know how to read

Expected results:
Be aware of the expected results, and with that, be able to analyze and understand the results.

Additional info:
Note. This is just a single report, but the idea of this BZ it's something that will answer a similar question to all the reports that we have, and also, including the new ones to come.

Comment 1 Dana Singleterry 2023-02-01 12:48:24 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Comment 2 Marek Hulan 2023-03-21 13:27:34 UTC
After chatting with PM (Dana) and TAM (Rick Greene), we agreed that we could introduce a new input switching between human and machine readable output. So instead of numerical representation, if user decides to use human readable output, the status would say the same as UI, e.g. "Pending" for build status or "Active" for configuration status. The original request was to provide a description for all shipper reports, that is already tracked as BZ 1994886, so this one only tracks the request for human readable form of Host - Statuses report.

Comment 3 Jeremy Lenz 2023-05-23 14:51:33 UTC
Created redmine issue https://projects.theforeman.org/issues/36426 from this bug

Comment 4 Bryan Kearney 2023-05-23 18:22:34 UTC
Upstream bug assigned to jlenz

Comment 5 Bryan Kearney 2023-05-23 18:22:37 UTC
Upstream bug assigned to jlenz

Comment 10 errata-xmlrpc 2024-04-23 17:13:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010