Feature #30664

"Installable Errata" in report template

Added by Nagoor Shaik almost 2 years ago. Updated 12 months ago.

Ready For Testing
Errata Management
Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


b'Cloned from \n\n1. Proposed title of this feature request\n "Installable Errata" in report template\n\n3. What is the nature and description of the request?\nIn the Report Template, there are 2 templates which could generate the errata by "Applicable Errata".\nHowever customer would like to show the hosts\' Errata by Installable, and they do not find any parameter/value of ":installable_errata" to use in template.\n\n4. Why does the customer need this? (List the business requirements here)\nTheir management and audit team require to review the errata and patching level every month, according to the published content view and environment that client hosts belong to. They have to use this report to ensure and prove that all critical/important errata have been installed.\n\n5. How would the customer like to achieve this? (List the functional requirements here)\nUsing Report Template to generate the "Installable errata" per host report CSV, and using spreadsheet filtering could be easily check which hosts are not in patch level.\nHaving the parameter ":installable_errata" and also the default installable errata report template could ease to generate and modify the report required.\n\n6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.\nCustomer could use the installable errata report template to generate the correct csv report. The number and shown installable errata should be as same as the client hosts shown under Content Hosts -> (specific hosts) -> Errata tab.\nUsing the parameter :installable_errata" in the report template could successfully include those errata in the report.\n\n7. Is there already an existing RFE upstream or in Red Hat Bugzilla?\nNo\n\n8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?\nTimeline, better to be before August 2019. The release target is RHEL6, 7 and 8.\n\n9. Is the sales team involved in this request and do they have any additional input?\nNo\n\n10. List any affected packages or components.\nInstallable Erratas\n\n11. Would the customer be able to assist in testing this functionality if implemented?\nNA'


#1 Updated by Nagoor Shaik almost 2 years ago

  • Subject changed from b'"Installable Errata" in report template' to "Installable Errata" in report template

#2 Updated by The Foreman Bot almost 2 years ago

  • Assignee set to Nagoor Shaik
  • Status changed from New to Ready For Testing
  • Pull request added

#3 Updated by John Mitsch almost 2 years ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.17.0

#4 Updated by John Mitsch almost 2 years ago

  • Target version changed from Katello 3.17.0 to Katello 3.18.0

#5 Updated by Jonathon Turel over 1 year ago

  • Target version changed from Katello 3.18.0 to Katello 4.0.0

#6 Updated by Justin Sherrill about 1 year ago

  • Target version changed from Katello 4.0.0 to Katello 4.1.0

#7 Updated by Jeremy Lenz 12 months ago

  • Triaged changed from Yes to No
  • Target version changed from Katello 4.1.0 to Katello 4.2.0

no activity since April; bumping to 4.2

#8 Updated by Samir Jha 12 months ago

  • Target version changed from Katello 4.2.0 to Katello Backlog

Moving this to backlog. The automation should add this to a release when the PR is updated.

#9 Updated by Samir Jha 12 months ago

  • Triaged changed from No to Yes

Also available in: Atom PDF