Main sync page throws error/warning upon completion of sync if capsules non-responsive
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1327292
Description of problem:
If a user has capsule(s) not currently connected to satellite, and content is synced, the content sync will complete but the UI will throw an error/warning, due to the capsule(s) not responding.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Sync a bunch of content to satellite. Subsequently sync this to your capsule as well.
2. Wait for some content to update in the repos, or trigger an update (i.e., add packages to a custom repo)
3. Attempt to sync repos within satellite itself.
Content syncs but error is thrown (see forthcoming screenshot)
We probably should not make sync success dependent on capsule responsiveness. This is especially relevant considering the new Capsule UX work. Capsules should have their own sync workflow.