Bug #14873

Main sync page throws error/warning upon completion of sync if capsules non-responsive

Added by John Mitsch over 3 years ago. Updated about 1 year ago.

Foreman Proxy Content
Target version:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:


Cloned from
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:

Associated revisions

Revision 750181d0 (diff)
Added by John Mitsch over 3 years ago

Fixes #14873 - Repo syncs shouldn't fail when a capsule is down (#6005)


#1 Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to John Mitsch
  • Pull request added

#2 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) set to 143

#3 Updated by John Mitsch over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF