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.
Bug 1219870 - re-registering a capsule can break the connection between the capsule and content host object that represent the capsule
Summary: re-registering a capsule can break the connection between the capsule and con...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1206352 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-08 14:13 UTC by Eric Helms
Modified: 2019-08-15 04:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:55:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Eric Helms 2015-05-08 14:13:29 UTC
Comment 1 Eric Helms 2015-05-08 14:13:31 UTC 
Created from redmine issue http://projects.theforeman.org/issues/10257
Comment 2 Eric Helms 2015-05-08 14:13:32 UTC 
Upstream bug assigned to ehelms
Comment 3 Eric Helms 2015-05-08 14:15:08 UTC 
This will also require http://projects.theforeman.org/issues/10426
Comment 4 Eric Helms 2015-05-08 14:15:39 UTC 
Currently there is no direct connection between a capsule and the
content host that represents it other than look ups by hostname during
certain operations. If the Capsule has been re-registered, then there
are situations where multiple content host records with the same hostname
can exist. This in turn can lead to a number of issues including the inability
to create repositories and sync content properly. This change adds a
system_id attribute to the smart proxy model. When a content host is created
a check is performed for any smart proxies with that hostname and the
two are associated (or re-associated if the smart proxy already had a
content host attached). This will also link an existing content host
to a smart proxy when the proxy is created.
Comment 7 Eric Helms 2015-05-12 18:38:33 UTC 
*** Bug 1206352 has been marked as a duplicate of this bug. ***
Comment 9 Tazim Kolhar 2015-05-15 10:16:07 UTC 
VERIFIED:
# rpm -qa | grep foreman
foreman-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
foreman-libvirt-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-postgresql-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-gce-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.12-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-vmware-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-compute-1.7.2.21-1.el7sat.noarch
foreman-debug-1.7.2.21-1.el7sat.noarch

steps :
re-registered a capsule 
it worked
Comment 10 Bryan Kearney 2015-08-11 13:29:28 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 11 Bryan Kearney 2015-08-12 13:55:50 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.