Red Hat Bugzilla – Bug 1394290
Could not find virtual machine network interface matching <ip address>
Last modified: 2017-03-09 09:19:27 EST
Description of problem: When customer try to provision new machines using distributed switch on vCenter they receive this message, although it's possible to provision using Standard switch. Version-Release number of selected component (if applicable): 6.2.2 (customer environment) Ps.: This customer came from 6.1.9 -> 6.2.2 How reproducible: 100% in customer env. Steps to Reproduce: 1. Create new host 2. Define all information about vm 3. Define the network to one specific distributed SW 4. Submit Actual results: Message below --- Unable to save Could not find virtual machine network interface matching 10.0.10.238 --- Expected results: Provision a new machine. Additional info:
Hello all Just one information about the project - http://projects.theforeman.org/issues/11106 Best Regards -- Waldirio M Pinheiro | Senior Software Maintenance Engineer
Connecting redmine issue http://projects.theforeman.org/issues/11106 from this bug
Upstream bug component is Compute Resources - VMWare
Created attachment 1221290 [details] patch to foreman to add more logging around vsphere networks. patch to foreman to add more logging around vsphere networks. To apply: cd /usr/share/foreman git init; git add -A .; git commit -m original patch -p1 < ~/vsphere-net-logging.patch service httpd restart Tested against sat 6.2.4, but should work with any 6.2.x version
Created attachment 1221291 [details] patch to foreman to change the way we identify the the network, when virtual switches in place. patch to foreman to change the way we identify the the network, when virtual switches in place. To apply: cd /usr/share/foreman git init; git add -A .; git commit -m original patch -p1 < ~/vsphere-net-logging.patch service httpd restart Tested against sat 6.2.4, but should work with any 6.2.x version
And of course, the second patch should have different name, such as vsphere-unique-networks.patch cd /usr/share/foreman git init; git add -A .; git commit -m original patch -p1 < vsphere-unique-networks.patch service httpd restart
I would like to ask to apply first the logging patch, try to provision, then the second one and try to provision again and at the end share /var/log/foreman/production.log with us
Created attachment 1221886 [details] output query
Created attachment 1222001 [details] patch to foreman to change the way we identify the the network to use key instead of managed object id patch to foreman to change the way we identify the the network to use network key instead of the managed object id. Please revert changes caused by previous patches attached to the bz first (as mentioned in the instructions below) cd /usr/share/foreman # in case not already managed by git git init; git add -A .; git commit -m original # in case some local changes were made before git checkout -- . patch -p1 < ~/vsphere-dvportgroup-key.patch service httpd restart
Upstream bug assigned to inecas@redhat.com
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:0447