Bug 2180222

Summary:	When retrieving compute profile information, it still spins for a while and eventually will fail for timeout
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Compute Resources - VMWare	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	ahumbe, ankulkar, chrobert, jwarnica, mhulan, rlavi, saydas
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
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:	2024-06-06 16:11:12 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 2023-03-20 23:40:40 UTC

Description of problem:
When retrieving compute profile information, it still spins for a while and eventually will fail for timeout. Note that for this environment, we can see a huge # of data centers (~750)

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

How reproducible:
100%

Steps to Reproduce:
1. Configure Satellite / Compute Resource and Compute Profile
2. Click over the Compute Profile and select the Compute Resource
3.

Actual results:
It will spend a long time before presenting something, eventually, timeout.

Expected results:
Be quick, once there is a filter by the datacenter

Additional info:

Comment 3 Ron Lavi 2023-03-27 12:00:57 UTC

*** Bug 2180887 has been marked as a duplicate of this bug. ***

Comment 5 Brad Buckingham 2023-03-27 13:18:53 UTC

Hi Waldirio,

Is this a regression from prior release?

Thanks!

Comment 6 Chris Roberts 2023-03-27 16:34:20 UTC

Hi Brad,

It is hard to say without testing. I don't think we ever hit a scenario with a customer that is at this scale. I would say it's not regression.

@Ron, I tested reverting the commit on Waldirio's box and it seems faster. As you can see from his update he was really digging into it, so not sure if he made any changes to the cache etc. I am going to test my devel box and see if the time looks better as well.

Comment 12 Eric Helms 2024-06-06 16:11:12 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.