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:
Not sure it is necessary to show a green notification everytime a RH is enabled/disabled. It feels sort of laggy, and I'm not sure it is necessary to show a notification every time for something that is basically a toggle.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Enable RH content
2. Provider > Red Hat > Enable Repos
3. Drill down into a product and select/enable/disable several repos in rapid succession
4. View UI
Actual results:
* A green "success" message pops up for each selection. The UI remains responsive. While there is a slight lag between select/deselect and the UI updating, this is reasonably acceptable. However the wait time between enabling/disabling and the subsequent success notification gives an impression of UI lagginess.
* User gets a success message for each select/deselect, which seems a bit excessive
Expected results:
* Don't show (log?) a success message each time a repo is enabled/disabled. Rather, only worry about errors and display/log them instead.
Additional info: