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:

It appears that under certain conditions, the ajaxComplete (katello.js) is not being invoked when an action is completed.  As a result, the spinner (both pointer and in the Katello banner) continues spinning.

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


How reproducible:
The behavior is inconsistent; therefore, not sure if it unique to environment or scenario.  It was observed w/ FF 3.6 and using the Katello demo server.

Steps to Reproduce:
1. go to Administration -> Roles
2. click New Role
3. enter a name
4. click Save
  
Actual results:
spinners continue to spin after role was added

Expected results:
spinners should stop after role was added

Additional info:

commit: 8e9c624db27bc24d24909fb10db5e0c98be7393b


After various testing and discussion with the team, the only scenario where I'm able to repro this is with the subscription file upload.  As a result, the change made actually only addresses that scenario.  If there are additional scenarios, where it is observed, we may need to re-open this BZ or create additional.

The scenarios addressed by this commit is:
1. go to Providers
2. select Red Hat provider
3. click Subscriptions
4. click Browse and enter a manifest
5. click Upload

Once the upload completes, observe the the spinners no longer spin.

This commit also addressed the same issue on an unsuccessful subscription file upload.

QA verified for both of these scenarios. Will keep an eye on other locations where this might occur/be occurring.

getting rid of 6.0.0 version since that doesn't exist