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.
I registered a vmware host to satellite, along with it being reported by virt-who. I then shortened its hostname. Next, I associated the host to it's corresponding vm in the compute resource, and made it managed by satellite. Then, I created/registered a new host with a hostname that is an expansion of the first host's short name.
At this point, I ran the unify hosts task. As a result, the hosts were correctly not unified.
Continuing, I unregistered the original host and managed the second, then re-ran the command.
-bash-4.1# foreman-rake katello:unify_hosts USE_NAME=true
...
Host dhcp-10-12-211-60.fake.domain.com is registered with subscription-manager but is managed, please un-unmanage this host first.
Verified in Satellite 6.2.9 Snap 2.
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-2017:1191