Ask Your Question
0

Build of instance aborted: Failed to allocate the network(s), not rescheduling. [closed]

asked 2018-05-19 06:08:06 -0500

liujunfei980 gravatar image

Hello,

When I use the pike version of OpenStack to create a virtual machine, I get an error message. Can you help me solve the problem? The openstack platform was built by kolla-ansible.

specific information: Fault Information: Build of instance f0e015bd-6957-4d35-a880-8ad31824a466 aborted: Failed to allocate the network(s), not rescheduling. Code: 500 Details:File "/var/lib/kolla/venv/lib/python2.7/site-packages/nova/compute/manager.py", line 1829, in _do_build_and_run_instance filter_properties) File "/var/lib/kolla/venv/ Lib/python2.7/site-packages/nova/compute/manager.py", line 2035, in _build_and_run_instance reason=msg)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-03-13 23:35:42 -0500

prerna.dembla gravatar image

updated 2019-03-13 23:39:51 -0500

I am facing the same error and using the same environment that is " openstack pike using Kolla-ansible".

When we create new VM it get created successfully sometime and sometime it end up in ERROR state, after remaining in BUILD state for a long time.

Controller node Error logs: ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'8fb8526f-1d5f-4413-900a-05758408e7a1', 'name': 'network-vif-plugged', 'server_uuid': u'8475034b-2691-4a59-ac30-7efd5f882a0d'}]: EndpointNotFound: Could not find requested endpoint in Service Catalog.

Build of instance aborted: Failed to allocate the network(s), not rescheduling.

Compute1 node Error logs:

WARNING nova.virt.libvirt.driver [req-2d194234-f330-4a01-a076-053859208e73 6cedd8d14f20443394f7cd64e1332ff8 f40a8ab69e6a41a7883b34fd71448d76 - default default] [instance: 9646559f-18e3-4420-ba47-e06020547bbf] Timeout waiting for vif plugging callback for instance with vm_state building and task_state spawning.: Timeout: 300 seconds

Instance failed to spawn: VirtualInterfaceCreateException: Virtual Interface creation failed nova/nova-compute.log:17412:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] Traceback (most recent call last): nova/nova-compute.log:17413:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2007, in _build_and_run_instance nova/nova-compute.log:17414:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] block_device_info=block_device_info) nova/nova-compute.log:17415:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2814, in spawn nova/nova-compute.log:17416:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] destroy_disks_on_failure=True) nova/nova-compute.log:17417:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5319, in _create_domain_and_network nova/nova-compute.log:17418:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] raise exception.VirtualInterfaceCreateException() nova/nova-compute.log:17419:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] VirtualInterfaceCreateException: Virtual Interface creation failed nova/nova-compute.log:17420:2019-03-13 11:41:17.891 7 ERROR nova.compute.manager [instance: c365b656-40d3-4396-af6f-50f646674406] nova/nova-compute.log:17423:2019-03-13 11:41:17.904 7 ERROR nova.compute.manager [req-9bb1fec6-0bb8-40cd-8e08-66a3e10aad53 8306c27de2a64eccbfb55838a0d79cef 00000000000003228460960090160000 - default default] [instance: c365b656-40d3-4396-af6f-50f646674406] Build of instance c365b656-40d3-4396-af6f-50f646674406 aborted: Failed to allocate the network(s), not rescheduling.: BuildAbortException: Build of instance c365b656-40d3-4396-af6f-50f646674406 aborted: Failed to allocate the network(s), not rescheduling.

kindly provide the possible solution.

edit flag offensive delete link more

Comments

Two suggestions:

  1. Format your error output as code, so that it becomes readable.
  2. You created an answer. To increase the chance that somebody answers, create a question.
Bernd Bausch gravatar imageBernd Bausch ( 2019-03-14 00:11:43 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2018-05-19 06:08:06 -0500

Seen: 269 times

Last updated: Mar 13