This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2280336 - Satellite WebUI shows incorrect Boot time value for registered hosts.
Summary: Satellite WebUI shows incorrect Boot time value for registered hosts.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infrastructure
Version: 6.15.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-14 09:34 UTC by Omkar
Modified: 2024-06-06 17:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:38:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-25096 0 None Migrated None 2024-06-06 17:38:54 UTC

Description Omkar 2024-05-14 09:34:38 UTC 
Description of problem:

Satellite WebUI shows incorrect value for Boot time for registered hosts.

Version-Release number of selected component (if applicable):

6.14
6.15

How reproducible:

100%

Steps to Reproduce:

1. Register the host to Satellite which has a boot time more than 1/2 Months

2. Go to Satellite WebUI --> Hosts --> All Hosts & check the value of "Boot Time" for the registered host.

Actual results:

The Boot time value shows the round up value.

** For Example:

If the host last reboot was on "20th March 2024" and if we check the boot time on "Satellite WebUI --> Hosts --> All Hosts" before the date "20th May 2024", It shows Boot Time as "2 months ago" which is not correct as it is yet to complete the 2 Months period.



Expected results:

The Boot time should show the correct value similar to the below commands from the host CLI to have the exact information instead of round up value.  

# uptime
OR
# uptime -p


Additional info:

NA
Comment 1 Ewoud Kohl van Wijngaarden 2024-05-14 12:19:26 UTC 
How it works is that a fact is uploaded, which is then normalized and stored as a host facet as a datetime.

After that it's up to the UI to present it. For that we rely on the react-intl.FormattedRelative component. Sadly we're on version 2.x of react-intl and the current version is 5.x so I have a hard time finding the exact API reference. It relies on https://www.npmjs.com/package/intl-relativeformat.

If I read it right, it has "interesting" thresholds. Quoting https://www.npmjs.com/package/intl-relativeformat?activeTab=code

RelativeFormat.thresholds = {
  second: 45,
  'second-short': 45, // seconds to minute
  minute: 45,
  'minute-short': 45, // minutes to hour
  hour: 22,
  'hour-short': 22, // hours to day
  day: 26,
  'day-short': 26, // days to month
  month: 11,
  'month-short': 11 // months to year
};

My analysis may be wrong, but this suggests to me that it rounds up quite aggressively.

However, I also see https://github.com/formatjs/formatjs/commit/9ca5270278578e4ae0f729242da4c8cfa7ed1fd1 (which is part of intl 1.1+ and we're on ~1.2.5).

Given these are very generic UI components, I'm changing the BZ component to Infrastructure (because I can't find a better place right now). I'm hoping Maria can shed some light on this.
Comment 2 Maria 2024-05-14 15:58:50 UTC 
The round up Ewoud found sounds correct, we also display the actual value in a tooltip if a user hovers the relative time, for example: "May 14 , 2024, 05:50 AM"
Comment 3 Eric Helms 2024-06-06 17:38:56 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.