In fact it seems that the list of network vlan in foreman is not correct.
For example, in vcenter we can choose something like: "VLAN 151 (dvSwitchProduction)"

But in Foreman we see 1 line for "VLAN 151", and 1 line for "dvSwitchProduction-DVUplinks137" … which is apparently the official name of the virtual switch.

There should be something wrong either in the UI, or in the query to the Vcenter.
We have multiple virtual Switches, so that could also explain the thing.

:)

We did a try on a different cluster, where we have only 1 virtual switch so network label is something like "VLAN 151" only.
Host is successfully created, with the good network label.

So I think with this we have all info needed to fix :)

Thx in advance;

The current released version of fog distributed virtual switches are not supported so they are creating as a traditional network. https://github.com/fog/fog/pull/1431 has been merged, but waiting for a release.

Confirmed it has nothing to do with foreman. I used the patch proposed above and it works perfectly.

To close IMHO.

Updated to foreman 1.2 rc2 but still having this problem, version of vmware is ESXi 5.1.0,914609

Peter Gustafsson wrote:

Updated to foreman 1.2 rc2 but still having this problem, version of vmware is ESXi 5.1.0,914609

Which version of ruby193-rubygem-fog?

1. rpm -qa | grep ruby193-rubygem-fog
   ruby193-rubygem-fog-1.11.1-3.el6.noarch

Peter: for this to properly work you need some permissions on the network devices. Are you admin or can you at least read the dvswitch and virtual port group?

Ewoud, My user has full admin rights.

It turned out that there were multiple networks with the same name in the VMware cluster, one ordinary and one drvgroup backed.
We renamed one of the network and now the network label is correct set during creation of the vm.

Br, Peter