Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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 1524622 - associate VM - MAC compare is case senstive
Summary: associate VM - MAC compare is case senstive
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.2.12
Hardware: Unspecified
OS: Unspecified
Target Milestone: 6.6.0
Assignee: Dominik Hlavac Duran
QA Contact: Vladimír Sedmík
: 1706998 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2017-12-11 18:15 UTC by Paul Dudley
Modified: 2021-03-11 16:36 UTC (History)
8 users (show)

Fixed In Version: foreman-1.22.0-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-22 19:47:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16520 0 Low Closed associate VM - MAC compare is case senstive 2021-02-17 15:38:00 UTC
Red Hat Knowledge Base (Solution) 4109661 0 None None None 2019-05-09 08:49:39 UTC

Description Paul Dudley 2017-12-11 18:15:33 UTC
Description of problem:
When trying to associate a vmware VM the following is hit:

Error: No host found to associate this VM with

Version-Release number of selected component (if applicable):

Additional info:
In vi /usr/share/foreman/app/models/compute_resources/foreman/model/vmware.rb change:

From this:
454-    def associated_host(vm)
455:      associate_by("mac", vm.mac)
456-    end

To this:
454-    def associated_host(vm)
455:      associate_by('mac', { |mac| Net::Validations.normalize_mac(mac) })
456-    end

It looks like this line would need to be changed for all other compute resource options as well.

Comment 2 Paul Dudley 2017-12-12 20:04:26 UTC
So far this change works just fine for vmware and libvirt compute resources, from tests done internally and by the customer.

Comment 3 Ondřej Pražák 2018-01-24 12:44:02 UTC
Connecting redmine issue from this bug

Comment 4 Bryan Kearney 2019-02-27 11:05:43 UTC
Upstream bug assigned to dhlavacd

Comment 5 Bryan Kearney 2019-03-31 14:05:53 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue has been resolved.

Comment 6 Diksha Chaudhari 2019-05-09 08:46:49 UTC
*** Bug 1706998 has been marked as a duplicate of this bug. ***

Comment 9 Bryan Kearney 2019-10-22 19:47:20 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.