Bug #17535
Associate a VMware VM to host with multiple NICs fails
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assigned To: |  Trey Dockendorf | ||
| Category: | Compute resources - VMware | ||
| Target version: | - | ||
| Difficulty: | Bugzilla link: | 1257611 | |
| Found in release: | 1.11.1 | Pull request: | https://github.com/theforeman/foreman/pull/4071 |
| Story points | - | ||
| Velocity based estimate | - | ||
| Release | 1.14.0 | Release relationship | Auto |
Description
A host with multiple NICs is failing to associate to a VMware VM because the primary NIC does not match the first MAC address returned by VMware. The simple solution is one implemented for oVirt compute resources, and that is to check all interface MACs for a host when performing associations.
Associated revisions
Fixes #17535 - Associate host with multiple NICs to VMWare VM
Fixes #17535 - Associate host with multiple NICs to VMWare VM
(cherry picked from commit 239609088ef8d0310c0f865e514d048c77d7cc26)
History
#1
Updated by Dominic Cleal over 1 year ago
- Category set to Compute resources - VMware
#2
Updated by The Foreman Bot over 1 year ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4071 added
#3
Updated by Trey Dockendorf over 1 year ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 239609088ef8d0310c0f865e514d048c77d7cc26.
#4
Updated by Ohad Levy over 1 year ago
- Bugzilla link set to 1257611
#5
Updated by Dominic Cleal over 1 year ago
- Assigned To set to Trey Dockendorf
- Release set to 1.14.0