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.
DescriptionMichael Rustenbach
2015-06-14 23:04:09 UTC
Created attachment 1038715[details]
Screenshot of bug result
Description of problem:
When attempting to add new puppet module, the web browser freezes and displays the following error:
A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.
Script: https://sat01.domainname/assets/application-fddb49ee45f2655204f3b8dfa194d5fc.js:18
In addition, all the puppet module names show up as {{ item.module_name }}
Because of this, there is no way to add puppet modules to the content view.
Version-Release number of selected component (if applicable):
In /var/log/messages there is the following error:
puppet-agent[12852]: (/File[/var/lib/puppet/lib]) Could not evaluate: Could not retrieve information from environment production source(s) puppet://sat01.domainname/plugins
How reproducible:
Steps to Reproduce:
1.Content -> Content Views
2.Select Content View
3.Click on Puppet Modules
4.Click on Add Module
Actual results:
Browser freezes, module names are listed as {{ item.module_name }} and there is no way to add a module to the content view.
Expected results:
Modules to be listed by name and to be able to select version of module.
Additional info:
Running Red Hat Enterprise Linux 6.6 with the latest updates. See attached screenshot
Comment 1Michael Rustenbach
2015-06-14 23:15:21 UTC
Tested with both Firefox ESR 38.0.1 and Google Chrome 43 (64-Bit) and same result.
Comment 2RHEL Program Management
2015-06-14 23:22:27 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 4Michael Rustenbach
2015-06-14 23:26:54 UTC
After waiting for about 20 minutes with Google Chrome, the modules did finally pull up by name. So it looks like it involves just taking a very long time for the modules to load. On a page refresh, I have to wait again for the 10-20 minute time for the modules to come up again.
Note: when testing the resolution for this bug, please ensure that the CLI is also able to list the puppet modules. Refer to bug 1266460, which raises the issue of possible request timeouts.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501