Red Hat Bugzilla – Bug 1327292
Main sync page throws error/warning upon completion of sync if capsules non-responsive
Last modified: 2016-09-14 17:00:08 EDT
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:
Created attachment 1147289 [details] main UI
Created attachment 1147290 [details] click thru to error
Upstream bug component is Capsule
Created redmine issue http://projects.theforeman.org/issues/14873 from this bug
Verified in Satellite 6.2.2 Snap 1.1. Temporarily took down the capsule's network interface. Confirmed that the Satellite was unable to communicate with it. Then sync'd 10 repositories, a mixture of custom and RH repos. All repos sync'd without issue.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1885