Bug 1741219

Summary:	subscription-manager fact for "last_boot" should indicate UTC
Product:	Red Hat Enterprise Linux 8	Reporter:	John Sefler <jsefler>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:	Red Hat subscription-manager QE Team <rhsm-qe>
Severity:	low	Docs Contact:
Priority:	low
Version:	8.1	CC:	bbuckingham, csnyder, haynesbr, jturel, wpinheir
Target Milestone:	rc	Keywords:	EasyFix, Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1928667 (view as bug list)		Environment:
Last Closed:	2021-02-14 07:30:09 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:
Bug Depends On:
Bug Blocks:	1928667

Description John Sefler 2019-08-14 14:08:59 UTC

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:

Comment 1 B. Haynes 2019-08-14 15:29:42 UTC

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

Comment 2 Chris Snyder 2019-08-15 15:11:01 UTC

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

Comment 5 Brad Buckingham 2021-02-09 11:06:47 UTC

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?

Comment 6 Jonathon Turel 2021-02-09 19:43:22 UTC

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

Comment 7 RHEL Program Management 2021-02-14 07:30:09 UTC

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.