Description of problem: When you generate a report template, it doesn't show any CSV headers (name, label, severity, etc...) on the top of the file if no results are found. This is just a blank file and is confusing as it makes one think the file wasn't generated correctly, also it may break automation that users build around this. We should keep the headers on the file even if its blank Version-Release number of selected component (if applicable): 6.5.0 How reproducible: Always Steps to Reproduce: 1.Navigate to Report Templates 2.Click "Generate" for applicable errata and search with a host that has no errata applicable (name = myhost). 3.view blank report Actual results: report is blank Expected results: report has headers Additional info:
There's the new helper that can be used in reports to define headers in Foreman 1.24. All we need to do is to update all report templates, so it has line like this <%- report_headers "name", "label", "severity" -%> That will make sure the report will print headers even if no data was gathered.
Created redmine issue https://projects.theforeman.org/issues/28637 from this bug
Upstream bug assigned to mhulan
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28637 has been resolved.
Verified with Sat 6.8 snap 2.1. 1. Generate "Host - Applicable errata" report without any arguments 2. Generate it with filter for a host without any applicable errata => The first one contains correct data, the second one contains an empty dataset with the same headers as the first one. Note that "Applied errata" template is an old version and this bug has been fixed in new versions of reports, e.g. "Host - Applicable errata". Whether this is correct or not is a different issue.
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.8 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-2020:4366