Comment 7 for bug 1678458

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 bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] vcpu limit not specified, defaulting to unlimited
  2017-04-01 04:15:45.501 7 INFO nova.compute.claims [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Claim successful
  2017-04-01 04:15:45.707 7 INFO nova.scheduler.client.report [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Submitted allocation for instance
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall [-] in fixed duration looping call
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall Traceback (most recent call last):
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_vmware/common/loopingcall.py", line 76, in _inner
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall self.f(*self.args, **self.kw)
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall File "/var/lib/kolla/venv/local/lib/python2.7/site-packages/oslo_vmware/api.py", line 440, in _poll_task
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall raise task_ex
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall VimFaultException: Invalid configuration for device '0'.
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall Faults: ['InvalidDeviceSpec']
  2017-04-01 04:15:49.719 7 ERROR oslo_vmware.common.loopingcall
  2017-04-01 04:15:49.721 7 ERROR nova.compute.manager [req-0d04189c-f822-4ac3-be8b-44b88f255acd bef1f8c56ef547339595ce46bbe0ec0e cf73ccda5d894a60b8bcc93c2cc4f20a - - -] [instance: d4d11aa3-9eb7-496b-9ad6-17703d58dd88] Instance failed to spawn

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1678458/+subscriptions