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.
Since this bugzilla was initially created, katello has been updated to be a 'rails engine' that runs within the foreman application. As part of this work, there has been some integration of the foreman host with the katello content host (formerly known as 'system'). With that integration, the foreman host is considered the 'master'. When a host is provisioned and the client registers back with the Satellite, a content host will be created and will be associated with the foreman host. If the client (i.e. content host) unregisters the content host will be deleted; however, it will not impact the foreman host (i.e. master). If, however, the foreman host is deleted, the corresponding content host will also be removed. This will allow the client to register/unregister without impacting the foreman host.
Based on the above, this bugzilla is no longer valid. In the future, the desire is to further integrate the host and content host, such that it is is really a single 'host'.