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.
Created attachment 1170825[details]
full traceback
Description of problem:
A capsule sync after an upgrade gives this error:
2016-06-21 20:37:52 [foreman-tasks/action] [E] Could not find Content Host with exact name 'capsule61-rhel7.example.com', verify the Capsule is registered with that name. (Katello::Errors::CapsuleContentMissingConsumer)
Version-Release number of selected component (if applicable):
satellite-6.2.0-17.0.el7sat.noarch
How reproducible:
Not sure
Steps to Reproduce:
1. On Sat 6.1, Sync some repos publish to library
2. Don't sync capsule (associate the capsule with dev environment) before upgrading to latest 6.2.
3. Upgrade the satellite and capsule to latest 6.2 version.
4. Trigger the capsule sync from satellite using capsule UI.
Actual results:
Error on sync
Expected results:
Sync runs successfully
Additional info:
In the upstream, a commit was submitted that removes the code that is causing this error. I have tested a downstream upgrade with that commit and am able to successfully perform the capsule sync after the upgrade.
The commit was part of upstream issue:
http://projects.theforeman.org/issues/12556
That issue includes 2 PRs; however, for downstream, we only want one of those. The PR that we want is:
https://github.com/Katello/katello/pull/6104
I am going to move this bug to POST; however, at this time I am not going to link the redmine to it, since I would only like to pull in 1 PR.
VERIFIED.
@satellite-6.2.0-21.1.el7sat.noarch
tfm-rubygem-katello-3.0.0.68-1.el7sat.noarch
used manual reproducer described in comment #0:
...
4. Trigger the capsule sync from satellite using capsule UI.
>>> it went fine, both for DEV and Library environments.
(first I synced DEV as it was untouched after upgrade to 6.2 and then switched capsule to Library and synced again another env)
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:1501
Created attachment 1170825 [details] full traceback Description of problem: A capsule sync after an upgrade gives this error: 2016-06-21 20:37:52 [foreman-tasks/action] [E] Could not find Content Host with exact name 'capsule61-rhel7.example.com', verify the Capsule is registered with that name. (Katello::Errors::CapsuleContentMissingConsumer) Version-Release number of selected component (if applicable): satellite-6.2.0-17.0.el7sat.noarch How reproducible: Not sure Steps to Reproduce: 1. On Sat 6.1, Sync some repos publish to library 2. Don't sync capsule (associate the capsule with dev environment) before upgrading to latest 6.2. 3. Upgrade the satellite and capsule to latest 6.2 version. 4. Trigger the capsule sync from satellite using capsule UI. Actual results: Error on sync Expected results: Sync runs successfully Additional info: