VMware: Invalid configuration for device '0' on instance lauch

Hi, I have some updates.
From my understanding, VCDriver will download vmdk image from glance, then upload the image to vmware datastore via vcenter. But I did not see the vmdk image in local nova cache, and remote datastore!
Why??

updates:
   I use neutron networking, but I don't have vmware NSX. Dose Neutron networking work without NSX?

And I found: vmops.build_virtual_machine() --> vm_util.create_vm() failed
The error is: oslo_vmware.exceptions [-] Fault InvalidDeviceSpec not matched.
So I dump the config_spec:

(VirtualMachineConfigSpec){
   changeVersion = None
   name = "cffbe917-0fd9-4161-90eb-89bed0f12d90"
   version = None
   uuid = None
   instanceUuid = "cffbe917-0fd9-4161-90eb-89bed0f12d90"
   npivNodeWorldWideName[] = <empty>
   npivPortWorldWideName[] = <empty>
   npivWorldWideNameType = None
   npivDesiredNodeWwns = None
   npivDesiredPortWwns = None
   npivTemporaryDisabled = None
   npivOnNonRdmDisks = None
   npivWorldWideNameOp = None
   locationId = None
   guestId = "ubuntu64Guest"
   alternateGuestName = None
   annotation = "name:v1
userid:bef1f8c56ef547339595ce46bbe0ec0e
username:admin
projectid:cf73ccda5d894a60b8bcc93c2cc4f20a
projectname:admin
flavor:name:m1.small
flavor:memory_mb:2048
flavor:vcpus:1
flavor:ephemeral_gb:0
flavor:root_gb:20
flavor:swap:0
imageid:b503bba4-7028-4402-a1cd-a406be13464f
package:15.0.1
"
   files =
      (VirtualMachineFileInfo){
         vmPathName = "[datastore1]"
         snapshotDirectory = None
         suspendDirectory = None
         logDirectory = None
         ftMetadataDirectory = None
      }
   tools =
      (ToolsConfigInfo){
         toolsVersion = None
         afterPowerOn = True
         afterResume = True
         beforeGuestStandby = True
         beforeGuestShutdown = True
         beforeGuestReboot = True
         toolsUpgradePolicy = None
         pendingCustomization = None
         syncTimeWithHost = None
         lastInstallInfo =
            (ToolsConfigInfoToolsLastInstallInfo){
               counter = None
               fault =
                  (LocalizedMethodFault){
                     fault =
                        (MethodFault){
                           faultCause =
                              (LocalizedMethodFault){
                                 localizedMessage = None
                              }
                           faultMessage[] = <empty>
                        }
                     localizedMessage = None
                  }
            }
      }
   flags =
      (VirtualMachineFlagInfo){
         disableAcceleration = None
         enableLogging = None
         useToe = None
         runWithDebugInfo = None
         monitorType = None
         htSharing = None
         snapshotDisabled = None
         snapshotLocked = None
         diskUuidEnabled = None
         virtualMmuUsage = None
         virtualExecUsage = None
         snapshotPowerOffBehavior = None
         recordReplayEnabled = None
         faultToleranceType = None
      }
   consolePreferences =
      (VirtualMachineConsolePreferences){
         powerOnWhenOpened = None
         enterFullScreenOnPowerOn = None
         closeOnPowerOffOrSuspend = None
      }
   powerOpInfo =
      (VirtualMachineDefaultPowerOpInfo){
         powerOffType = None
         suspendType = None
         resetType = None
         defaultPowerOffType = None
         defaultSuspendType = None
         defaultResetType = None
         standbyAction = None
      }
   numCPUs = 1
   numCoresPerSocket = 1
   memoryMB = 2048
   ...

So anybody can tell me what's wrong with the config spec? Thanks a lot.

Hi,I meet the same error,did you solve it?
Thanks.

Could you please provide the vpxd.log from vCenter when this error occurs?
Do you get the same error when using the cirros image?
Are you using Neutron with DVS or NSX plugin?

Hi,

Attached is the vpxd log file,and please focus on the error start at time 2017-10-16T09:29:29.437+08:00.

I get the same error whein using the cirros image.

I am not using the DVS or NSX plugin,i am using the Neutron network ML2 plugin with openvswith mechanism driver only.

Looking forward for your help,thank you very much.

Regards
Jim

________________________________
发件人: <email address hidden> <email address hidden> 代表 Radoslav Gerganov <email address hidden>
发送时间: 2017年10月13日 15:52
收件人: <email address hidden>
主题: [Bug 1678458] Re: VMware: Invalid configuration for device '0' on instance lauch

Could you please provide the vpxd.log from vCenter when this error occurs?
Do you get the same error when using the cirros image?
Are you using Neutron with DVS or NSX plugin?

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1678458

Title:
  VMware: Invalid configuration for device '0' on instance lauch

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Hi, I foud an issue.
    my deployment: Ocata release (depolyed by kolla-ansbile) + vmware vcenter 6.0
    I have configured nova.conf to use vmware VCDirver. and the session is set up correctly.
    I use "openstack image create ..." to import official ubuntu-16.04 image. (qemu-img convet it form qcow2 to spare vmdk format.
    Everything is ok for now.
    But when I luanch instance, error happend, the log is below:

  2017-04-01 04:15:45.496 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Attempting claim: memory 2048 MB, disk 20 GB, vcpus 1 CPU
  2017-04-01 04:15:45.497 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Total memory: 28640 MB, used: 512.00 MB
  2017-04-01 04:15:45.498 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] memory limit: 42960.00 MB, free: 42448.00 MB
  2017-04-01 04:15:45.499 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Total disk: 1921 GB, used: 0.00 GB
  2017-04-01 04:15:45.499 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] disk limit: 1921.00 GB, free: 1921.00 GB
  2017-04-01 04:15:45.500 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Total vcpu: 12 VCPU, used: 0.00 VCPU
  2017-04-01 04:15:45.501 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef5473...

I have resolved this problem.The instance create fail because it must use Distributed Switch for the vCenter to launch the instance from OpenStacn Mitaka version.So it must use the vmware-nsx network plugin for VMware hypervisor.You can use the following link to install and configure vmware-nsx network plugin.

https://github.com/cybercom-finland/neutron_vmware_dvswitch

I had the same mistake. How did you solve it?

This is nova-compute log
2018-02-22 07:19:42.899 5 DEBUG oslo_service.periodic_task [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Running periodic task ComputeManager._check_instance_build_time run_periodic_tasks /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_service/periodic_task.py:215
2018-02-22 07:19:42.901 5 DEBUG oslo_service.periodic_task [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Running periodic task ComputeManager.update_available_resource run_periodic_tasks /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_service/periodic_task.py:215
2018-02-22 07:19:42.948 5 DEBUG nova.compute.resource_tracker [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Auditing locally available compute resources for kolla (node: domain-c7.A9A92EE9-9488-4840-9F21-57E5EFC9B133) update_available_resource /var/lib/kolla/venv/lib/python2.7/site-packages/nova/compute/resource_tracker.py:640
2018-02-22 07:19:42.960 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-26019f35-1067-4fdc-b728-48979804b0b5 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:42.991 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-ff16a8b0-3c64-4223-a827-529c0001c246 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.026 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-72206dab-5421-411b-9c7f-9e8576c95a2e request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.065 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-ffa55cf0-bed9-4ffd-99aa-1fa56c616590 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.619 5 DEBUG oslo_vmware.service [-] Invoking PropertyCollector.RetrievePropertiesEx with opID=oslo.vmware-c3c5fd57-dc15-421a-97bd-f8021fa3aa96 request_handler /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_vmware/service.py:354
2018-02-22 07:19:43.660 5 DEBUG nova.compute.resource_tracker [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Hypervisor/Node resource view: name=domain-c7.A9A92EE9-9488-4840-9F21-57E5EFC9B133 free_ram=1374MB free_disk=39GB free_vcpus=2 pci_devices=None _report_hypervisor_resource_view /var/lib/kolla/venv/lib/python2.7/site-packages/nova/compute/resource_tracker.py:776
2018-02-22 07:19:43.661 5 DEBUG oslo_concurrency.lockutils [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Lock "compute_resources" acquired by "nova.compute.resource_tracker._update_available_resource" :: waited 0.000s inner /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:270
2018-02-22 07:19:43.749 5 DEBUG nova.scheduler.client.report [req-45d0db1a-2606-4758-9250-483843662b11 - - - - -] Refreshing aggregate associations for resource provider 838382f7-e055-4b4d-9ae5-45ffcdde2ffd _ensure_resource_provider /var/lib/kolla/venv/lib/python2.7/site-packages/nova/scheduler/client/report.py:498
2018-02-2...

Hello,

The instance create fail because it must use Distributed Switch for the vCenter to launch the instance from OpenStacn Mitaka version.So it must use the vmware-nsx network plugin for VMware hypervisor.You can use the following link to install and configure vmware-nsx network plugin.You can follow this guide below to configure.

https://github.com/cybercom-finland/neutron_vmware_dvswitch

[https://avatars1.githubusercontent.com/u/6649135?s=400&v=4]<https://github.com/cybercom-finland/neutron_vmware_dvswitch>

GitHub - cybercom-finland/neutron_vmware_dvswitch: VMware ...<https://github.com/cybercom-finland/neutron_vmware_dvswitch>
github.com
neutron_vmware_dvswitch - VMware dvSwitch mech driver for OpenStack Neutron ML2 plugin

Regards
Jimmy

________________________________
发件人: <email address hidden> <email address hidden> 代表 lws <email address hidden>
发送时间: 2018年2月22日 9:51
收件人: <email address hidden>
主题: [Bug 1678458] Re: VMware: Invalid configuration for device '0' on instance lauch

I had the same mistake. How did you solve it?

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1678458

Title:
  VMware: Invalid configuration for device '0' on instance lauch

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Hi, I foud an issue.
    my deployment: Ocata release (depolyed by kolla-ansbile) + vmware vcenter 6.0
    I have configured nova.conf to use vmware VCDirver. and the session is set up correctly.
    I use "openstack image create ..." to import official ubuntu-16.04 image. (qemu-img convet it form qcow2 to spare vmdk format.
    Everything is ok for now.
    But when I luanch instance, error happend, the log is below:

  2017-04-01 04:15:45.496 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Attempting claim: memory 2048 MB, disk 20 GB, vcpus 1 CPU
  2017-04-01 04:15:45.497 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Total memory: 28640 MB, used: 512.00 MB
  2017-04-01 04:15:45.498 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] memory limit: 42960.00 MB, free: 42448.00 MB
  2017-04-01 04:15:45.499 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Total disk: 1921 GB, used: 0.00 GB
  2017-04-01 04:15:45.499 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] disk limit: 1921.00 GB, free: 1921.00 GB
  2017-04-01 04:15:45.500 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b8...