Ask Your Question
0

Boot instance failed with error 'Instance failed network setup'

asked 2015-03-24 00:42:34 -0500

William gravatar image

updated 2015-03-25 01:36:11 -0500

I deployed an openstack by using one server as both controller/network node and another as compute node, follows openstack install-guide. All verification passed until I finished neutron installation/configuration and tried to launch an instance for testing.

It always failed with error on network setup, instance stuck in error status and can't be deleted, content in /var/log/nova/nova-compute.log attached below.

2015-03-24 10:47:31.218 32574 AUDIT nova.compute.manager [req-6a0db069-b46a-4e9d-8360-aaff5cd7e160 None] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] Starting instance...
2015-03-24 10:47:31.275 32574 AUDIT nova.compute.claims [-] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] Attempting claim: memory 512 MB, disk 1 GB
2015-03-24 10:47:31.275 32574 AUDIT nova.compute.claims [-] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] Total memory: 144716 MB, used: 2048.00 MB
2015-03-24 10:47:31.276 32574 AUDIT nova.compute.claims [-] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] memory limit: 217074.00 MB, free: 215026.00 MB
2015-03-24 10:47:31.276 32574 AUDIT nova.compute.claims [-] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] Total disk: 49 GB, used: 3.00 GB
2015-03-24 10:47:31.276 32574 AUDIT nova.compute.claims [-] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] disk limit not specified, defaulting to unlimited
2015-03-24 10:47:31.285 32574 AUDIT nova.compute.claims [-] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] Claim successful
2015-03-24 10:47:31.634 32574 INFO nova.virt.libvirt.driver [-] [instance: 3f84e1ed-eacf-4d09-9059-c84941798090] Creating image
2015-03-24 10:47:31.694 32574 WARNING nova.virt.disk.vfs.guestfs [-] Unable to force TCG mode, libguestfs too old? 'GuestFS' object has no attribute 'set_backend_settings'
2015-03-24 10:47:34.104 32574 WARNING nova.virt.disk.vfs.guestfs [-] Failed to close augeas aug_close: do_aug_close: you must call 'aug-init' first to initialize Augeas
2015-03-24 10:48:31.448 32574 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager Traceback (most recent call last):
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1646, in _allocate_network_async
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager     dhcp_options=dhcp_options)
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 48, in wrapped
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager     return func(self, context, *args, **kwargs)
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/base_api.py", line 61, in wrapper
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager     res = f(self, context, *args, **kwargs)
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 283, in allocate_for_instance
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager     nw_info = self.network_rpcapi.allocate_for_instance(context, **args)
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/rpcapi.py", line 190, in allocate_for_instance
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager     macs=jsonutils.to_primitive(macs))
2015-03-24 10:48:31.448 32574 TRACE nova.compute.manager   File ...
(more)
edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2015-03-24 11:09:46 -0500

dbaxps gravatar image

updated 2015-03-25 23:47:12 -0500

Try in nova.conf

vif_plugging_is_fatal: false
vif_plugging_timeout: 0

View https://ask.openstack.org/en/question...
Looks like such kind of message is generated by some empty table in nova database.

edit flag offensive delete link more

Comments

Have read the topic before the post and there is tables in nova DB, tables list added in previous post.

William gravatar imageWilliam ( 2015-03-25 01:47:27 -0500 )edit
0

answered 2015-03-24 11:17:54 -0500

I'm not sure exactly what your issue is but you can take a look at this previously reported issue. It may assist in pointing you in the right direction. Does the instance produce any console logs, if so can you post them.

https://ask.openstack.org/en/question...

edit flag offensive delete link more

Comments

The log didn't report any package loss, I added the output of virsh nwfilter-list in previous post. Also error pop up when I try console-log.

ERROR (NotFound): Unable to get console (HTTP 404) (Request-ID: req-ae12aa84-f22b-4d36-a414-0ec9f52bba64)
William gravatar imageWilliam ( 2015-03-25 01:32:12 -0500 )edit
0

answered 2015-03-25 22:41:21 -0500

William gravatar image

Cause found on settings in /etc/nova/nova.conf at compute nood, by reconfigure this part I can go forward, however, new error occurred as reported "VirtualInterfaceCreateException: Virtual Interface creation failed", still working on it.

[DEFAULT]
...
network_api_class = nova.network.neutronv2.api.API
security_group_api = neutron
linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
firewall_driver = nova.virt.firewall.NoopFirewallDriver
edit flag offensive delete link more

Comments

VIF problem resolved by correct value of nova_admin_tenant_id in neutron.conf from name to UUID. Now instances are correctly booted.

nova_admin_tenant_id = SERVICE_TENANT_ID
William gravatar imageWilliam ( 2015-03-25 23:30:30 -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: 2015-03-24 00:31:23 -0500

Seen: 3,640 times

Last updated: Mar 25 '15