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.

Description of problem:


When running the applied errata report the last reboot time is incorrect and report downloading never asks for a location to Download.


How reproducible:

Every time we run a report template of Applied errata.


Steps to Reproduce:
1. Apply an errata on the client.
2. Reboot the client system
3. Run the applied errata report

Actual results:

Last reboot time is incorrect.

date,hostname,erratum_id,erratum_type,status,last_reboot_time
2019-08-20 10:43:15 +0530,mindy-dottavio.lab.example.com,RHBA-2019:2404,bugfix,success,1970-01-01 07:26:13 +0530

No location asked to save the file.


Expected results:
It should show the correct reboot time and ask for a location to save the file.


Additional info:

These are clearly two separate and unrelated issues, please pick one and open separate BZ for the second. Note that the last reboot information is based on uptime fact coming from various sources. The immediate reboot does not mean we get the fresh information. There needs to ocure at least one puppet agent run in order to get updated value. In your example, it looks like wrongly calculated value, we had an issue with btime fact parsing, that was coming from subscription manager. You haven't specified which version/snap you encounter the issue with, so it's hard to tell, whether it's not a duplicate.

This is the fact parsing issue for the reference https://bugzilla.redhat.com/show_bug.cgi?id=1732317