Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Bug 1787729

Summary: Applied Errata report no longer works when last reboot is included
Product: Red Hat Satellite Reporter: Marek Hulan <mhulan>
Component: ReportingAssignee: Samir Jha <sajha>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: egolov, mhulan, oprazak, sajha, tbrisker
Target Milestone: 6.7.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.14.0.13-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:28:12 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 Marek Hulan 2020-01-04 19:49:44 UTC 
Description of problem:

When I render applied errata report, rendering fails with the message "Association named 'uptime_fact' was not found on Host::Managed; perhaps you misspelled it?"


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

6.7

How reproducible:

100%

Steps to Reproduce:
1. render Applied Errata report
2. make sure to set Include Last Reboot to yes

Actual results:

Error printed

Expected results:

It should render the report with last reboot information

Additional info:

This is caused by the refactoring of reported data facet, we no longer use facts for uptime/last reboot information. The logic in "load_errata_applications" macro defined in Katello needs to be updated. See https://github.com/theforeman/foreman/pull/6843 for more details.

This would be a regression
Comment 4 Tomer Brisker 2020-02-18 08:42:34 UTC 
Created redmine issue https://projects.theforeman.org/issues/29042 from this bug
Comment 5 Bryan Kearney 2020-02-27 19:02:36 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29042 has been resolved.
Comment 7 Lukáš Hellebrandt 2020-03-11 13:43:16 UTC 
Verified with Sat 6.7 snap 15 using reproducer from OP.
Comment 10 errata-xmlrpc 2020-04-14 13:28:12 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, 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:1454