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.
Description of problem:
I am not aware of the reasons here, but we are unable to load smart-proxy page on automation-box
Version-Release number of selected component (if applicable):
sat62-snap5
How reproducible:
Reproducible only on a box which runs sat6qe's automation.
Looks like the automation populates lot of entities, which makes the smart-proxy index page not able to load.
Steps to Reproduce:
1.
2.
3.
Actual results:
Cannot load smart-proxy index page after running automation with the sat6.
Expected results:
Should be able to load smart-proxy index page.
Additional info:
Hi Kedar,
It seems this bug was filed against an early snap for Satellite 6.2.
Could you confirm this is still an issue?
If so, please provide a production.log with debug enabled showing the failed attempt to load the smart proxies page as well as any error displayed to the user.