RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
Introduced by the implementation of RFE Bug 1478892 is a new system fact called "last_boot" which gives the time that the system was most recently booted.

To clarify the units of time, please use this bug to append suffix "UTC"


Version-Release number of selected component (if applicable):
[root@kvm-02-guest25 ~]# rpm -q subscription-manager
subscription-manager-1.25.13-1.el8.x86_64

[root@kvm-02-guest25 ~]# rpm -q subscription-manager --changelog | grep 1478892
- 1478892: Add in a last_boot fact for parity with spacewalk facts


How reproducible:


Steps to Reproduce:
[root@kvm-02-guest25 ~]# subscription-manager facts | grep last_boot
last_boot: 2019-08-12 12:29:10


Actual results:
last_boot time is reported without an indicator of the units of time.  Is it GMT? EST? EDT? UTC?  The answer is UTC.

Expected results:
last_boot: 2019-08-12 12:29:10 UTC

Additional info:

I notice that this is limited to RHEL8.   Please make this "last_boot" fact avail for RHEL7 systems also.

If subman includes the "UTC" timezone in the last_boot fact, will this disrupt satellite's consumption of this fact?

Chris, I am not aware of any negative impacts that would result from changing the timezone to UTC for the "last_boot" fact.

Jonathon, can you also take a look and confirm if there are any concerns?

Should be fine considering that we don't surface that fact explicitly anywhere in the UI or API

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.