Bug 1893456

Summary:	Multiple/Old Entries on Insights inventory are causing error in subscription watch counting
Product:	Red Hat Hybrid Cloud Console (console.redhat.com)	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Inventory	Assignee:	Muhammad Arif <aarif>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Rodrigo Antunes <rantunes>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aprice, bkearney, cmarinea, ihands, khowell, lphiri
Target Milestone:	---	Keywords:	Reopened, SubscriptionWatch, UserExperience
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-27 17:56:19 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:

Description Waldirio M Pinheiro 2020-10-31 18:28:27 UTC

Description of problem:
Once we can see multiple entries on Insights inventory that has been there for ~2 months (time to be removed by the system), this "old" information will be processed as well by swatch, providing the wrong counting at the end of the day.

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


How reproducible:
100%

Steps to Reproduce:
1. Checking the old information on insights inventory
2. Checking the information on swatch
3.

Actual results:
We can see entries with last seen long ago ...

Expected results:
Once we are pushing every single day new information to the Insights inventory, I believe the rule to keep the old entries should be at least 1 week (or less, maybe 3 days. Entries older that should be removed automatically)

Additional info:

Comment 7 Greg McCullough 2020-11-02 21:41:45 UTC

This is likely a similar issue as reported in bug 1889520.  See https://bugzilla.redhat.com/show_bug.cgi?id=1889520#c3

Comment 8 Waldirio M Pinheiro 2020-11-02 21:51:53 UTC

(In reply to Greg McCullough from comment #7)
> This is likely a similar issue as reported in bug 1889520.  See
> https://bugzilla.redhat.com/show_bug.cgi?id=1889520#c3

Agree. If you want, we can close this one as duplicated.

Thank you!
Waldirio

Comment 9 Waldirio M Pinheiro 2020-11-02 21:52:35 UTC


*** This bug has been marked as a duplicate of bug 1889520 ***

Comment 12 aprice 2021-09-27 17:17:46 UTC

This was addressed by our de-duplication changes, along with the reporter sending us a shorter fresh/stale period.
Unless you're still able to reproduce the issue, I think this can be closed.