Project

General

Profile

Bug #2188

Vmware/VSphere 4.1 - Provision host - Network label not set correctly

Added by Florent Delvaille almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Host creation
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Ahoi,

When provisionning a host within foreman using Vmware 4.1 update 3, the host is created correctly except the NIC part.
We are using Foreman 1.1-stable.

When checking the NIC details in VCenter, this is what we got:

As you can see, the Summary is correct, but the Network label (which is actually the important one) is empty.
This makes the host not bootable …

History

#1 Updated by Florent Delvaille almost 7 years ago

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.

:)

#2 Updated by Florent Delvaille almost 7 years ago

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;

#3 Updated by Ewoud Kohl van Wijngaarden almost 7 years ago

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.

#4 Updated by Florent Delvaille almost 7 years ago

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

To close IMHO.

#5 Updated by Ohad Levy almost 7 years ago

  • Status changed from New to Resolved
  • Priority changed from High to Normal
  • Target version set to 1.2.0

#6 Updated by Peter Gustafsson over 6 years ago

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

#7 Updated by Dominic Cleal over 6 years ago

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?

#8 Updated by Peter Gustafsson over 6 years ago

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

#9 Updated by Dominic Cleal over 6 years ago

  • Status changed from Resolved to New

#10 Updated by Ewoud Kohl van Wijngaarden over 6 years ago

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?

#11 Updated by Dmitri Dolguikh over 6 years ago

  • Assignee set to Dmitri Dolguikh

#12 Updated by Peter Gustafsson over 6 years ago

Ewoud, My user has full admin rights.

#13 Updated by Peter Gustafsson over 6 years ago

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

#14 Updated by Dominic Cleal over 6 years ago

  • Status changed from New to Closed
  • Assignee deleted (Dmitri Dolguikh)
  • % Done changed from 0 to 100

Also available in: Atom PDF