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 2254807 - On Red Hat Satellite "boot_time <" parameter populates the search results with incorrect values on Hosts ---> All Hosts page
Summary: On Red Hat Satellite "boot_time <" parameter populates the search results wit...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Search
Version: 6.13.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-16 10:18 UTC by Anand Jambhulkar
Modified: 2024-01-16 10:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-01-16 10:58:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Search-3daysago.png (113.92 KB, image/png)
2023-12-16 10:18 UTC, Anand Jambhulkar 		no flags Details
Query - "3 days" (165.37 KB, image/png)
2023-12-16 10:21 UTC, Anand Jambhulkar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-21981 0 None None None 2023-12-16 10:19:24 UTC
Red Hat Knowledge Base (Solution) 7049432 0 None None None 2023-12-16 10:35:04 UTC

Description Anand Jambhulkar 2023-12-16 10:18:45 UTC 
Created attachment 2004565 [details]
Search-3daysago.png

Description of problem:
----------------------

If we input the query with "boot_time < "3 days ago"" or "boot_time < "3 days"", the host booted over 3 days ago will be listed as well.



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

Red Hat Satellite Web UI Search Field



How reproducible:
----------------

Very easily reproducible



Steps to Reproduce:
------------------

1. Go to Satellite Web UI. ---> Hosts ---> All Hosts ---> In the search box, type - boot_time < "3 days ago" OR type boot_time < "3 days"



Actual results:
--------------

It shows the hosts booted over 3 days ago as well.



Expected results:
----------------

The search results page should populate with entries of the hosts whose boot time was less than "n" days ago.



Additional info:
---------------

I have attached the following 2 screenshots of the Satellite Web UI which shows the issue -

   1. Search-3daysago.png

   2. Search-3days.png
Comment 1 Anand Jambhulkar 2023-12-16 10:21:42 UTC 
Created attachment 2004566 [details]
Query - "3 days"
Comment 2 Adam Ruzicka 2024-01-16 10:58:17 UTC 
I'd say this works as expected. When you do 'boot_time < "3 days ago"', you compare two points in time, not intervals. The search doesn't translate to "give me hosts which booted less than three days ago", but rather to "give me a list of hosts which booted on a day that has smaller date than the day three days ago". For example let's say I have a host that booted yesterday (2023-01-15) and I search for 'boot_time < "3 days ago"'. In this context, 3 days ago would be 2023-01-13. For this particular host, the search would translate to '2023-01-15 < 2023-01-13' which is not true, so the host wouldn't be listed. It is a bit clunky, but it's not exactly wrong.

If you want machines which booted in the last 3 days, you should use 'boot_time >= "3 days ago"'.
Note You need to log in before you can comment on or make changes to this bug.