Bug 1743495 - [Snap 16] Report-template not asking for location to save file and Last reboot time is incomplete.
Summary: [Snap 16] Report-template not asking for location to save file and Last reboo...
Keywords:
Status: CLOSED DUPLICATE of bug 1732317
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.6.0
Hardware: All
OS: All
high
urgent
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-20 06:49 UTC by maneesh verma
Modified: 2019-09-26 20:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-26 20:22:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1732317 0 unspecified CLOSED "Uptime: about 49 years" for a host without facts 2021-02-22 00:41:40 UTC

Description maneesh verma 2019-08-20 06:49:39 UTC
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:

Comment 3 Marek Hulan 2019-08-20 09:30:09 UTC
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.

Comment 4 Marek Hulan 2019-08-20 09:32:14 UTC
This is the fact parsing issue for the reference https://bugzilla.redhat.com/show_bug.cgi?id=1732317


Note You need to log in before you can comment on or make changes to this bug.