Project

General

Profile

Actions

Bug #10657

open

Foreman does not use the correct vsphere distributed switch name

Added by rui fernandes almost 9 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

In vsphere, the distributed switch name is: DVM-1600 (DSwitch-1)
Foreman displays: DVM-1600

Once the host is created foreman, I have to:
  • go to the vsphere console and edit the host object
  • set the network FROM: "DVM-1600", TO: "DVM-1600 (DSwitch-1)"
  • power off/on the host
  • after this host is fine
This first time I go to vsphere console:
  • I see "DVM-1600" in the network settings
    vphere setting right host is created by foreman
  • After I select "DVM-1600 (DSwitch-1)" and restart the host, the "DVM-1600" option nolonger appears in the vsphere network settings.
    vsphere network setting after I fix the host and reboot

These are the names as seen from foreman:
the network names as see by foreman

Here are a few log entries:

2015-05-31 18:08:02 [D]   Host::Managed Load (0.7ms)  SELECT "hosts".* FROM "hosts" WHERE "hosts"."uuid" = '501f6e51-27dd-ab97-a32c-872a41373eb0' LIMIT 1
2015-05-31 18:08:02 [D] Orchestration::Compute: Trying to match network interfaces from fog   <Fog::Compute::Vsphere::Interfaces
    server_id="501f6e51-27dd-ab97-a32c-872a41373eb0" 
    [
                  <Fog::Compute::Vsphere::Interface
        mac="00:50:56:9f:e0:e0",
        network="DVM-1600",
        name="Network adapter 1",
        status="untried",
        summary="DVM-1600",
        type=VirtualVmxnet3,
        key=4000,
        virtualswitch=nil,
        server_id="501f6e51-27dd-ab97-a32c-872a41373eb0" 
      >    
    ]
  >
2015-05-31 18:08:02 [D] Orchestration::Compute: nic #<Nic::Managed id: nil, mac: nil, ip: "10.92.17.100", type: "Nic::Managed", name: "test-vm-8.dev.marinsw.net", host_id: nil, subnet_id: 4, domain_id: 1, attrs: {}, created_at: nil, updated_at: nil, provider: nil, username: nil, password: nil, virtual: false, link: true, identifier: "", tag: "", attached_to: "", managed: true, mode: "balance-rr", attached_devices: "", bond_options: "", primary: true, provision: true, compute_attributes: {"type"=>"VirtualVmxnet3", "network"=>"DVM-1600"}> assigned to   <Fog::Compute::Vsphere::Interface
    mac="00:50:56:9f:e0:e0",
    network="DVM-1600",
    name="Network adapter 1",
    status="untried",
    summary="DVM-1600",
    type=VirtualVmxnet3,
    key=4000,
    virtualswitch=nil,
    server_id="501f6e51-27dd-ab97-a32c-872a41373eb0" 
  >

Files

vsphere-network.png View vsphere-network.png 70.3 KB vphere setting right host is created by foreman rui fernandes, 05/31/2015 03:33 PM
foreman-view.png View foreman-view.png 37.8 KB the network names as see by foreman rui fernandes, 05/31/2015 03:34 PM
vsphere-network2.png View vsphere-network2.png 72.1 KB vsphere network setting after I fix the host and reboot rui fernandes, 05/31/2015 03:36 PM
Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Category set to Compute resources - VMware
  • translation missing: en.field_release deleted (56)

Which version of Foreman are you using? Are you doing network or image based provisioning?

Actions #2

Updated by rui fernandes almost 9 years ago

I have just upgraded to foreman 1.8.1 had the same issue in version 1.7.3.

I am doing to a network install

Actions

Also available in: Atom PDF