Actions
Bug #4307
closed
New VMware VM creation does not respect NIC type selection
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
Updated by Matt Chesler almost 11 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
Updated by Anonymous almost 11 years ago
- Category set to VM management
- Assignee set to Martin Matuška
Martin, could you take a look?
Updated by Dominic Cleal almost 11 years ago
- Related to Feature #3116: NIC type selection for vSphere added
Updated by Ewoud Kohl van Wijngaarden almost 11 years ago
- Related to Bug #4324: VMware NIC type incorrectly shows E1000 instead of vmxnet3 added
Updated by Dominic Cleal almost 11 years ago
- Has duplicate Bug #4342: VMXNET3 not working in 1.4.0 for VMWare Compute Resource added
Updated by Dominic Cleal almost 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
Updated by Martin Matuška almost 11 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 461e6b003bc00d6d62e20d8f1c5e5c860ebdaaba.
Actions