Project

General

Profile

Bug #4307

New VMware VM creation does not respect NIC type selection

Added by Matt Chesler over 5 years ago. Updated about 1 year ago.

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

Description

Creating a new NIC through either the Web UI or hammer and specifying Vmxnet3 as the NIC type results in a new VM with an E1000 NIC. Running Foreman 1.4, Hammer 0.18


Related issues

Related to Foreman - Feature #3116: NIC type selection for vSphereClosed2013-09-18
Related to Foreman - Bug #4324: VMware NIC type incorrectly shows E1000 instead of vmxnet3Closed2014-02-12
Has duplicate Foreman - Bug #4342: VMXNET3 not working in 1.4.0 for VMWare Compute ResourceDuplicate2014-02-13

Associated revisions

Revision 461e6b00 (diff)
Added by Martin Matuška over 5 years ago

fixes #4307 New VMware VM creation does not respect NIC type selection

Revision ed278520 (diff)
Added by Martin Matuška over 5 years ago

fixes #4307 New VMware VM creation does not respect NIC type selection

(cherry picked from commit 461e6b003bc00d6d62e20d8f1c5e5c860ebdaaba)

History

#1 Updated by Matt Chesler over 5 years ago

This is an RPM based installation, upgraded from Foreman 1.3.2

Relevant RPM versions:

ruby193-rubygem-fog.noarch 1.19.0-1.el6 @foreman
rubygem-hammer_cli.noarch 0.0.18-1.el6 @foreman
rubygem-hammer_cli_foreman.noarch 0.0.18-1.el6 @foreman
foreman.noarch 1.4.0-1.el6 @foreman

#2 Updated by Michael Moll over 5 years ago

  • Category set to VM management
  • Assignee set to Martin Matuška

Martin, could you take a look?

#3 Updated by Dominic Cleal over 5 years ago

#4 Updated by Ewoud Kohl van Wijngaarden over 5 years ago

  • Related to Bug #4324: VMware NIC type incorrectly shows E1000 instead of vmxnet3 added

#5 Updated by Dominic Cleal over 5 years ago

  • Has duplicate Bug #4342: VMXNET3 not working in 1.4.0 for VMWare Compute Resource added

#6 Updated by Dominic Cleal over 5 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 1.9.1
  • Legacy Backlogs Release (now unused) set to 5

#7 Updated by Martin Matuška over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF