Ask Your Question
3

icehouse - Virtual Interface creation failed

asked 2014-04-10 08:04:32 -0500

eupub gravatar image

updated 2014-04-10 21:50:10 -0500

Hi there,

I have installed icehouse on CentOS 6.5 and now trying create an instance but encounter this error:

Message: Virtual Interface creation failed Code: 500 Details:

File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 296, in decorated_function return function(self, context, *args, **kwargs) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2073, in run_instance do_run_instance() File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 249, in inner return f(*args, **kwargs) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2072, in do_run_instance legacy_bdm_in_spec) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1205, in _run_instance notify("error", fault=e) # notify that build failed File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1189, in _run_instance instance, image_meta, legacy_bdm_in_spec) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1333, in _build_instance network_info.wait(do_raise=False) File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1309, in _build_instance set_access_ip=set_access_ip) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 399, in decorated_function return function(self, context, *args, **kwargs) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1721, in _spawn LOG.exception(_('Instance failed to spawn'), instance=instance) File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1718, in _spawn block_device_info) File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2251, in spawn block_device_info) File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3654, in _create_domain_and_network raise exception.VirtualInterfaceCreateException()

api.log: 2014-04-11 10:38:36.383 6386 ERROR nova.api.openstack.wsgi [-] Exception handling resource: multi() got an unexpected keyword argument 'body' 2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi Traceback (most recent call last): 2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi File "/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py", line 983, in _process_stack 2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi action_result = self.dispatch(meth, request, action_args) 2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi File "/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py", line 1070, in dispatch 2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi return method(req=request, **action_args) 2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi TypeError: multi() got an unexpected keyword argument 'body' 2014-04-11 10:38:36.383 6386 TRACE nova.api.openstack.wsgi

compute.log: 2014-04-11 10:38:32.869 17049 ERROR nova.compute.manager [req-7c8f2ee8-f957-4f1e-b188-2f136fcb7cdb 1cfbc71fddb848668295a2bb1895dfda 9f03371fd9fb4ef8ba5760a3ae1021ba ... (more)

edit retag flag offensive close merge delete

Comments

try upgrading python to 2.7 or later.

SGPJ gravatar imageSGPJ ( 2014-04-10 13:30:54 -0500 )edit

I have added new logs from api.log and compute.log - please see if it rings any bells?

eupub gravatar imageeupub ( 2014-04-10 21:51:41 -0500 )edit

I've been having this issue for about a week now. I'm going to try the suggestion below.

elmiko gravatar imageelmiko ( 2014-04-14 15:30:20 -0500 )edit

Hi, Thanks for the update we have been able to launch instance with the change "vfi" parameter in nova.conf in both controller and compute nodes.

AMIT SAHA gravatar imageAMIT SAHA ( 2014-12-11 07:00:12 -0500 )edit

3 answers

Sort by ยป oldest newest most voted
5

answered 2014-04-13 19:58:04 -0500

eupub gravatar image

updated 2014-04-15 04:36:32 -0500

I fixed the problem by updating neutron.conf at controller to include neutron-nova interactions config which is missing at Open vSwitch OVS plugin - configure controller node

# openstack-config --set /etc/neutron/neutron.conf DEFAULT \
  notify_nova_on_port_status_changes True
# openstack-config --set /etc/neutron/neutron.conf DEFAULT \
  notify_nova_on_port_data_changes True
# openstack-config --set /etc/neutron/neutron.conf DEFAULT \
  nova_url http://controller:8774/v2
# openstack-config --set /etc/neutron/neutron.conf DEFAULT \
  nova_admin_username nova
# openstack-config --set /etc/neutron/neutron.conf DEFAULT \
  nova_admin_tenant_id SERVICE_TENANT_ID
# openstack-config --set /etc/neutron/neutron.conf DEFAULT \
  nova_admin_password NOVA_PASS
# openstack-config --set /etc/neutron/neutron.conf DEFAULT \
  nova_admin_auth_url http://controller:35357/v2.0

After adding these, the problem went away. Thanks for the hint!

Regards, Boon Lee

edit flag offensive delete link more

Comments

This worked for me as well. The only difference is that I am using a packstack --allinone configuration and I needed to use values from my keystonerc_admin file for the auth stuff. thanks!

elmiko gravatar imageelmiko ( 2014-04-15 12:18:03 -0500 )edit

This didn't work for me, any other solutions?

smenon78 gravatar imagesmenon78 ( 2014-04-21 13:28:50 -0500 )edit

I have solved my similar situation by adding vif plugin entries in the nova.conf under [DEFAULT] section

vif_plugging_is_fatal: false

vif_plugging_timeout: 0

Hope this helps

imfaisal87 gravatar imageimfaisal87 ( 2014-05-21 08:18:07 -0500 )edit

Making this change worked for me. Be sure to make this change on all hosts.

BergBrains gravatar imageBergBrains ( 2014-06-05 10:58:49 -0500 )edit

Using Neutron GRE with ML2,

Still having this issue after applying the two suggested fixes to both the compute node and the controller. Timing out after Neutron creates the port and attaches it to the instance, but fails to notify Nova that the port has been attached.

server.log:2014-07-30 08:50:11.711 26001 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'ad5184bc-aa95-4fd9-bc3a-37a37a943bfa', 'name': 'network-vif-unplugged', 'server_uuid': u'43854901-28f6-47a5-9720-6a464d2f4c3f'}]

Which of these is the right port?

Authorization URL for connection to nova in admin context. nova_admin_auth_url = http://135.21.103.72:5000/v2.0

or,

Authorization URL for connection to nova in admin context. nova_admin_auth_url = http://135.21.103.72:35357/v2.0

Spyderdyne gravatar imageSpyderdyne ( 2014-07-30 10:33:55 -0500 )edit
1

answered 2014-05-21 08:20:20 -0500

imfaisal87 gravatar image

My problem was not solved even after neutron.conf entries.

Then after adding these vif plugin entries in the nova.conf under [DEFAULT] section

vif_plugging_is_fatal: false

vif_plugging_timeout: 0

My problem was solved.

edit flag offensive delete link more
0

answered 2014-04-11 01:48:01 -0500

scouw gravatar image

I think you have to configure a new part of neutron.conf file. It's relative to comunication beetwen neutron and nova. Nova now implementa a new api https://blueprints.launchpad.net/nova/+spec/admin-event-callback-api (EventAPI).

edit flag offensive delete link more

Comments

Hi there, are you able to tell me specifically where in new neutron.conf?

eupub gravatar imageeupub ( 2014-04-13 04:39:42 -0500 )edit

I fixed the problem by updating neutron.conf at controller to include neutron-nova interactions config which is missing at Open vSwitch OVS plugin - configure controller node

# openstack-config --set /etc/neutron/neutron.conf DEFAULT \ notify_nova_on_port_status_changes True # openstack-config --set /etc/neutron/neutron.conf DEFAULT \ notify_nova_on_port_data_changes True # openstack-config --set /etc/neutron/neutron.conf DEFAULT \ nova_url http://controller:8774/v2 # openstack-config --set /etc/neutron/neutron.conf DEFAULT \ nova_admin_username nova # openstack-config --set /etc/neutron/neutron.conf DEFAULT \ nova_admin_tenant_id SERVICE_TENANT_ID # openstack-config --set /etc/neutron/neutron.conf DEFAULT \ nova_admin_password NOVA_PASS # openstack-config --set /etc/neutron/neutron.conf DEFAULT \ nova_admin_auth_url http://controller:35357/v2.0

After adding these, the problem went away. Thanks for the hint!

Regards, Boon Lee

eupub gravatar imageeupub ( 2014-04-13 19:57:19 -0500 )edit
1

I have configured neutron to ML2 plugin. How to configure these options to neutron.conf when ML2 in place.

T N S gravatar imageT N S ( 2014-04-22 00:23:28 -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

4 followers

Stats

Asked: 2014-04-10 08:04:32 -0500

Seen: 7,798 times

Last updated: May 21 '14