Bug #14873
closed
Main sync page throws error/warning upon completion of sync if capsules non-responsive
Description
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):
SNAP 7.1
How reproducible:
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.
Actual results:
Content syncs but error is thrown (see forthcoming screenshot)
Expected results:
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.
Additional info:
Updated by The Foreman Bot almost 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to John Mitsch
- Pull request https://github.com/Katello/katello/pull/6005 added
Updated by Eric Helms over 8 years ago
- Translation missing: en.field_release set to 143
Updated by John Mitsch over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|750181d05c2e8de93d1a59bc72727c7f26abd58e.