Project

General

Custom queries

Profile

Actions
Copy link

Bug #4307

closed

New VMware VM creation does not respect NIC type selection

Added by Matt Chesler over 11 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Martin Matuška
Category:
VM management
Target version:
1.4.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 3 (0 open — 3 closed)

Related to Foreman - Feature #3116: NIC type selection for vSphereClosedMartin Matuška09/18/2013Actions
Related to Foreman - Bug #4324: VMware NIC type incorrectly shows E1000 instead of vmxnet3ClosedMartin Matuška02/12/2014Actions
Has duplicate Foreman - Bug #4342: VMXNET3 not working in 1.4.0 for VMWare Compute ResourceDuplicate02/13/2014Actions
#2

Updated by Anonymous over 11 years ago

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

Updated by Dominic Cleal over 11 years ago

#4

Updated by Ewoud Kohl van Wijngaarden over 11 years ago

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

Updated by Dominic Cleal over 11 years ago

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

Updated by Dominic Cleal over 11 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 1.9.1
  • Translation missing: en.field_release set to 5
#7

Updated by Martin Matuška over 11 years ago

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

Also available in: Atom PDF