Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Verifying against a RHEL7.9 compose...
[root@hpe-dl380pgen8-02-vm-4 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.9 Beta (Maipo)
[root@hpe-dl380pgen8-02-vm-4 ~]# rpm -q subscription-manager
subscription-manager-1.24.32-1.el7.x86_64
[root@hpe-dl380pgen8-02-vm-4 ~]#
[root@hpe-dl380pgen8-02-vm-4 ~]# rpm -q subscription-manager --changelog | grep 1739695 -B20
* Tue Aug 13 2019 Christopher Snyder <csnyder> 1.24.14-1
- 1739706: Proper messaging of syspurpose add-addons
(jhnidek)
- 1739707: GUI: Do not auto-attach, when golden ticket is used
(jhnidek)
- 1705017: Show in man page that --installed is the default for the list
command (wpoteat)
- 1737894: syspurpose attributes in list --consumed
(jhnidek)
- 1737894: Print roles and usage in list of subscriptions
(jhnidek)
- 1739705: Don't print traceback during list --available
(jhnidek)
- 1724712: Updating from System Type to Entitlement Type (waldirio)
- 1739699: Fixed unsetting syspurpose attributes (jhnidek)
- 1723803: Print reasons, why syspurpose status is mismatch
(jhnidek)
- 1652549: Addition of tests for heartbeat method (wpoteat)
- 1652549: Connection method for hypervisor heartbeat (wpoteat)
- 1739695: Add in a last_boot fact for parity with spacewalk facts
Technically, this bug appears to be fixed in subscription-manager-1.24.14-1 which was already included in the shipped patches for RHEL-7.8
Verification Test...
[root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager facts | grep last_boot
last_boot: 2020-04-13 12:12:48
[root@hpe-dl380pgen8-02-vm-4 ~]# cat /proc/uptime
19486.23 38555.44
^^^^^^^^ This is the time in seconds of uptime
[root@hpe-dl380pgen8-02-vm-4 ~]# date -u
Mon Apr 13 17:37:58 UTC 2020
Apr 13 at 17:37 UTC minus 19486.23 divide by 60sec/min divide by 60min/hour = 5.4 hours which occurred on approximately Apr 13 at 12:13 UTC which nicely matches the last_boot fact.
VERIFIED: the last_boot fact is being collected and correctly reflects the time at which the proc uptime started counting.
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 (subscription-manager bug fix update), 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/RHBA-2020:3866