Project

General

Profile

Bug #26279

Foreman shows incorrect vmware interface type in network settings

Added by Olmo Rupert over 1 year ago. Updated over 1 year ago.

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

Description

Foreman created vsphere objects using VMXNET3 interface.

It correctly does so.

However, when looking up the respective server's network settings in foreman it shows that vsphere interface type
E1000 is being used. After verifying inside vsphere it correctly used VMXNET3.

So for some weird, possibly hardcoded reason it shows up as using E1000 instead of VMXNET3 in both the network interface overview, as inside the network interface whe you select Edit.

VirtualE1000 @ network-somenumber..

NIC: E1000

PowerCLI C:\> get-vm -Name te-k8-olmo202.df1.my.net | get-networkadapter

Name                 Type       NetworkName  MacAddress         WakeOnLan
                                                                  Enabled
----                 ----       -----------  ----------         ---------
Network adapter 1    Vmxnet3    kbrnts-1006  00:xxxx:5f:00       True
Network adapter 2    Vmxnet3    core-depl... 00:xxxxx:95:bc       True

Related issues

Related to Foreman - Bug #26280: The network used is different from the one visible in the network modal.Closed

History

#1 Updated by Marek Hulán over 1 year ago

May be related to #26280

#2 Updated by Marek Hulán over 1 year ago

  • Related to Bug #26280: The network used is different from the one visible in the network modal. added

Also available in: Atom PDF