yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #24946
[Bug 1397489] [NEW] VM boot failure since nova to neutron port notification fails
Public bug reported:
When I run the latest devstack and use nova boot to create a VM,but it
failed.
Nova show the VM,it show:"message": "Build of instance cb509a04-ca8a-
491f-baf1-be01b15f4946 aborted: Failed to allocate the network(s), not
rescheduling.", "code": 500, "details": " File
\"/opt/stack/nova/nova/compute/manager.py\", line 2030, in
_do_build_and_run_instance
and the following error in the nova-compute.log:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1714, in _spawn
block_device_info)
File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2266, in spawn
block_device_info)
File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3681, in _create_domain_and_network
raise exception.VirtualInterfaceCreateException()
VirtualInterfaceCreateException: Virtual Interface creation failed
Adding "vif_plugging_is_fatal = False" and "vif_plugging_timeout = 5" to
the compute nodes stops the missing message from being fatal and guests
can then be spawned normally and accessed over the network.
In the bug: https://bugs.launchpad.net/nova/+bug/1348103 says it
happened in cells environment,but it doesn't happen only in cells
environment.This problem should arouse our attention more.
** Affects: nova
Importance: Undecided
Status: New
** Tags: nova
** Project changed: neutron => nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1397489
Title:
VM boot failure since nova to neutron port notification fails
Status in OpenStack Compute (Nova):
New
Bug description:
When I run the latest devstack and use nova boot to create a VM,but it
failed.
Nova show the VM,it show:"message": "Build of instance cb509a04-ca8a-
491f-baf1-be01b15f4946 aborted: Failed to allocate the network(s), not
rescheduling.", "code": 500, "details": " File
\"/opt/stack/nova/nova/compute/manager.py\", line 2030, in
_do_build_and_run_instance
and the following error in the nova-compute.log:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1714, in _spawn
block_device_info)
File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2266, in spawn
block_device_info)
File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3681, in _create_domain_and_network
raise exception.VirtualInterfaceCreateException()
VirtualInterfaceCreateException: Virtual Interface creation failed
Adding "vif_plugging_is_fatal = False" and "vif_plugging_timeout = 5"
to the compute nodes stops the missing message from being fatal and
guests can then be spawned normally and accessed over the network.
In the bug: https://bugs.launchpad.net/nova/+bug/1348103 says it
happened in cells environment,but it doesn't happen only in cells
environment.This problem should arouse our attention more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1397489/+subscriptions
Follow ups
References