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:
Currently, if you try to sync something (i.e., a RH repo) and you get an error for whatever reason, the sync UI shows "Error", but there's no context to tell What Went Wrong.

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


How reproducible:


Steps to Reproduce:
1.  Create a RH provider/product etc., and try to sync it.  do /something/ that causes it to fail.
2.  View the Sync UI.  Note the "Error" message for the result.
3.  View the Notifications UI.
  
Actual results:
No way to tell what was the actual root of the error

Expected results:
* Indications in the Notifications UI and possibly notification popups
* Maybe the ability to hover/click on the error to get a tooltip indicating the issue?

Additional info:

What was actually done on this bz?

mass ON_QA move

QA verified while testing a separate, and possibly duplicitous, issue. Notifications are now sent when syncs have problems.