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.
DescriptionJustin Sherrill
2016-10-27 21:15:44 UTC
Description of problem:
Under some situations when dealing with the duplicate host problem, one or both of the hosts do not have a mac address. This makes the existing unify_hosts script not work properly since it is based on mac addresses for safety. We need a way to run it based purely on hostnames.
Its not clear how to get into this situation.
Version-Release number of selected component (if applicable):
6.2.2
Comment 8sthirugn@redhat.com
2017-01-09 22:17:29 UTC
Verified in Satellite 6.2.7 Snap 1.0
I used a customer database to test this:
1. `foreman-rake katello:unify_hosts` is run as part of the satellite upgrade process and it removed few duplicate hosts.
2. I ran `foreman-rake katello:unify_hosts USE_NAME=true` - It unified 18 hosts.
3. Also in the process I tested with option `DRYRUN=true` - It worked great just listing the affected hosts without making the database.
4. Note: I had 20 shortnamed hosts without the corresponding longnamed host entries, so I fixed them manually.
Comment 10sthirugn@redhat.com
2017-01-09 22:19:00 UTC
@Justin: Can you check if you are okay with the verification steps in Comment 8.
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:0197