Bug #6348
closedProvision host from image in VMware: wrong NIC type
Description
Hi Folks,
When I deploy a new machine from an image in VMware, I select the VMXNET3 adapter, however, when it's done cloning the image to a guest, the NIC is set to E1000. I've indented the logging line from the production log below, somewhat anonimized:
reproduction
- I've created a new compute profile, setting the network adapter to VMXNET3,
- Created a new host using the SLES10SP4 image;
- The machine is properly cloned in VMware;
- The machine is powered on;
- Our new guest starts up, without an eth0 interface,
- Looking at the settings of the guest leads to the conclusion that the E1000 adapter has been assigned instead of the VMXNET3 adapter.
Foreman production log
Started POST "/hosts" for 10.0.256.50 at 2014-06-24 08:59:02 +0200 Processing by HostsController#create as */* Parameters: { "utf8" => "รข", "authenticity_token" => "AAoCQo0BHhQCRk8xVjxFg05zH4txsZTC4N7aocD11q0=", "host" => { "name" => "<Server_name>", "hostgroup_id" => "12", "compute_resource_id" => "3", "compute_profile_id" => "20", "environment_id" => "9", "puppet_ca_proxy_id" => "1", "puppet_proxy_id" => "1", "config_group_ids" => [""], "puppetclass_ids" => [""], "managed" => "true", "progress_report_id" => "[FILTERED]", "type" => "Host::Managed", "compute_attributes" => { "cpus" => "1", "corespersocket" => "2", "memory_mb" => "768", "cluster" => "<cluster>", "path" => "/Datacenters/vm", "guest_id" => "sles10_64Guest", "interfaces_attributes"=> {" new_interfaces" => { "type" => "VirtualE1000", "network" => "dvportgroup-19631", "_delete" => "" }, "0" => { "type" => "VirtualVmxnet3", "network" => "dvportgroup-768", "_delete" => "" } }, "volumes_attributes" => { "new_volumes" => { "datastore" => "<datastore>", "name" => "Hard disk", "size_gb" => "10", "thin" => "true", "_delete" => "" }, "0" => { "datastore" => "<datastore>", "name" => "Hard disk", "size_gb" => "100", "thin" => "true", "_delete" =>"" } }, "scsi_controller_type" => "VirtualLsiLogicController", "start" => "1", "image_id" => "Templates/Linux/SLES10SP4-TMPL-v1.0" }, "domain_id" => "1", "realm_id" => "", "mac" => "", "subnet_id" => "1", "ip" => "<ipaddress>", "interfaces_attributes" => { "new_interfaces" => { "_destroy" => "false", "type" => "Nic::Managed", "mac" => "", "name" => "", "domain_id" => "", "ip" => "", "provider" => "IPMI" } }, "architecture_id" => "1", "operatingsystem_id" => "9", "provision_method" => "image", "build" => "1", "medium_id" => "", "ptable_id" => "", "disk" => "", "root_pass" => "[FILTERED]", "is_owned_by" => "9-Users", "enabled" => "1", "model_id" => "", "comment" => "", "overwrite" => "false" }, "capabilities" => "build image", "provider" => "Vmware"} Adding Compute instance for <hostname> Successfully decrypted field for Foreman::Model::Vmware <vmhost> Successfully decrypted field for Foreman::Model::Vmware <vmhost>
Relevant data:
Foreman version: 1.5.1
Fog version : 1.2.0
OS : CentOS 6.5
Kernel : 2.6.32-431.11.2.el6.x86_64
Updated by Dominic Cleal about 10 years ago
- Category changed from Compute resources to Compute resources - VMware
Updated by Anonymous over 9 years ago
- Related to Bug #10087: Deploying vmware from template ignores nic_type (E1000 or vmxnet3) setting, and configures using E1000 added
Updated by Dominic Cleal over 9 years ago
- Status changed from New to Duplicate
Although this was first, the other ticket has a PR associated already so we'll carry on using that ticket. Please track progress on #10087.