Project

General

Profile

Bug #4324

VMware NIC type incorrectly shows E1000 instead of vmxnet3

Added by Ewoud Kohl van Wijngaarden about 5 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

When I edit a VM in Foreman 1.4.0-1.el6, it shows both NICs are E1000 while in fact they are vmxnet3.


Related issues

Related to Foreman - Bug #4307: New VMware VM creation does not respect NIC type selectionClosed2014-02-10
Has duplicate Foreman - Bug #4933: Incorrect NIC type for VMware hostsClosed2014-03-28
Blocked by Foreman - Tracker #4582: Upgrade to fog > 1.20Closed

History

#1 Updated by Ewoud Kohl van Wijngaarden about 5 years ago

  • Related to Bug #4307: New VMware VM creation does not respect NIC type selection added

#2 Updated by Dominic Cleal about 5 years ago

Confirmed.

#3 Updated by marcelo veglienzone about 5 years ago

The same applies to the hard disk, no matter what you mark it's always set to thin provisioning ( it even happens when modifying the compute profile, it always goes back to thin )

#4 Updated by Dominic Cleal about 5 years ago

marcelo veglienzone wrote:

The same applies to the hard disk, no matter what you mark it's always set to thin provisioning ( it even happens when modifying the compute profile, it always goes back to thin )

The thin provisioning option should be fixed via #4159 in Foreman 1.4.1.

#5 Updated by marcelo veglienzone about 5 years ago

Just saw the new version which supposedly fixed all this

#7 Updated by Michael Moll about 5 years ago

  • Status changed from New to Pending

Setting this to pending. This depends on a new version of fog to be released and set for foreman to be used.

#8 Updated by Dominic Cleal about 5 years ago

#9 Updated by Dominic Cleal about 5 years ago

  • Has duplicate Bug #4933: Incorrect NIC type for VMware hosts added

#10 Updated by Dominic Cleal almost 5 years ago

  • Status changed from Pending to Closed
  • Assignee set to Martin Matuška
  • Target version set to 1.8.4
  • % Done changed from 0 to 100
  • Legacy Backlogs Release (now unused) set to 4

Also available in: Atom PDF