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:
When user toggles an option in Activation Key > Product Content, the backend is slow to respond, but user has no indication of this in the UI. User can end up selecting and trying to toggle the item multiple times but it never actually changes until the backend change has been made. Very confusing user experience.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150324.0
How reproducible:
Steps to Reproduce:
1. Create an activation key and assign content to it
2. go to the Activation Key > Product Content subtab.
3. Attempt to toggle various products/repos within the list that appears.
Actual results:
User can toggle multiple times, seemingly to no avail, until the backend triggers a refresh on the UI
Expected results:
Either we should be more responsive and/or flip it independent of the backend processing, or we should include some sort of spinner while the toggle is processing.
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/13919 has been closed
-------------
Thomas McKay
Applied in changeset commit:katello|c4c9e97ef752b2ae5355ef45708cff8fa45e59f7.
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