Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
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:
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