Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionWaldirio 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:
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.
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.