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.
DescriptionWaldirio M Pinheiro
2016-11-11 15:09:41 UTC
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:
Comment 2Waldirio M Pinheiro
2016-11-11 15:32:19 UTC
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
Comment 37Waldirio M Pinheiro
2016-11-18 14:57:50 UTC
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
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
Comment 66Red Hat Bugzilla
2023-09-15 00:00:30 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days