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 have a custom product/repo pointing at https://forge.puppetlabs.com and fully synchronized with 3200+ modules. Whenever I attempt to add a puppet module to a content view, from the moment I click the Puppet Module tab (of my selected content view) to the moment I can actually use the web UI to select a puppet module or even click anywhere else) it takes a few minutes on my Firefox web browser. The API call to grab all puppet module names takes less than 3 seconds, but rendering the results back into the web page brings the browser to its knees.

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

* Satellite-6.1.0-RHEL-6-20150303.0

How reproducible:


Steps to Reproduce:
1. Create a custom product and repo pointing to https://forge.puppetlabs.com
2. Sync the repo
3. Create a content view and try to add a random puppet module from the web ui

Actual results:

The web browser gets pegged for a couple of minutes and you cannot click on anything


Expected results:


Additional info:

Is there any sort of workaround for this atm or should I just add "wait for the browser to reload" or something similar to the release note?

If no rel note is required, pls remove the rel note blocker flag.

thanks

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