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 .
Bug 2164079 - Inventory is setting the "stale" date to a pretty weird date
Summary: Inventory is setting the "stale" date to a pretty weird date
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Hybrid Cloud Console (console.redhat.com)
Classification: Red Hat
Component: Inventory
Version: unspecified
Hardware: All
OS: All
low
low
Target Milestone: ---
: ---
Assignee: aprice
QA Contact: fstavela
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-24 17:46 UTC by Waldirio M Pinheiro
Modified: 2023-04-19 09:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-19 09:58:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHINENG-359 0 None None None 2023-04-19 09:58:52 UTC

Description Waldirio M Pinheiro 2023-01-24 17:46:41 UTC 
Description of problem:
There are some entries in the HBI that should not be around anymore. However, the stale_timestamp it's something like "2260-01-01T00:00:00+00:00"

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


How reproducible:
100%

Steps to Reproduce:
1. Checking for systems in our environment greater than 60 days
2.
3.

Actual results:
Some entries will be around

Expected results:
No entries, once the stale should be removed in 30 days, if I'm not wrong.

Additional info:
Comment 2 aprice 2023-01-24 18:29:03 UTC 
Nope, I actually don't think that's on your side. One of the requirements for Edge hosts in the Inventory is that they don't become stale or get automatically removed by Reaper. If a host has system_profile.host_type="edge", it sets the staleness timestamp far into the future. I don't recall why that *particular* date was chosen, though.
Comment 6 Insights Rule Dev Team 2023-04-19 08:27:03 UTC 
This bugzilla ticket has been migrated to https://issues.redhat.com/browse/RHINENG-359 for further development. Please follow the updates in that Jira ticket directly. This bugzilla ticket is marked as CLOSED. If the Jira ticket is not visible to you, please leave a comment in this bugzilla ticket.
Note You need to log in before you can comment on or make changes to this bug.