Ask Your Question
0

Instance failed with "binding_failed" error on RHEL7 Openstack Icehouse [closed]

asked 2015-01-04 23:25:46 -0500

updated 2015-01-08 02:46:49 -0500

Hi All,

I checked many similar query and I updated my configuration files for Compute and Neutron using below url. But having same (vif_type=binding_failed) issue. I shared my all Nova and Neutron Configuration files with recent log. I can understand there small bug I couldn't find out. Please check my configuration files and request to give a solution.

image descriptionhttps://ask.openstack.org/en/question... https://kashyapc.fedorapeople.org/vir...

Neutron Log
    server.log (grep -i error  nova-compute.log | tail -f)
    ~~~~~~~~~~~~~~~~~~~~~~~
2015-01-07 23:46:05.039 1387 INFO neutron.wsgi [req-f6093f47-e8e4-41f7-9c6e-2cfab124cd7d None] 192.168.2.52 - - [07/Jan/2015 23:46:05] "GET //v2.0/ports.json?tenant_id=9d70490f1dfe4b88bfab45f552a27e75&device_id=da048196-baf7-426c-9e06-ff1f6cd218eb HTTP/1.1" 200 202 0.009181
2015-01-07 23:46:05.080 1387 INFO neutron.wsgi [req-f6093f47-e8e4-41f7-9c6e-2cfab124cd7d None] (1387) accepted ('192.168.2.52', 54412)
2015-01-07 23:46:05.093 1387 INFO neutron.wsgi [req-b40e2862-a0b9-4744-9135-3174045fa774 None] 192.168.2.52 - - [07/Jan/2015 23:46:05] "GET //v2.0/networks.json?tenant_id=9d70490f1dfe4b88bfab45f552a27e75&shared=False HTTP/1.1" 200 912 0.012133
2015-01-07 23:46:05.095 1387 INFO neutron.wsgi [req-b40e2862-a0b9-4744-9135-3174045fa774 None] (1387) accepted ('192.168.2.52', 54413)
2015-01-07 23:46:05.104 1387 INFO neutron.wsgi [req-21e12733-622a-4c17-b5d7-b1eac5cf7a0c None] 192.168.2.52 - - [07/Jan/2015 23:46:05] "GET //v2.0/networks.json?shared=True HTTP/1.1" 200 205 0.008562

    Nova Log
    nova-compute.log (grep -i error  server.log | tail -f)
    ~~~~~~~~~~~~~~~~~~~~~~~
2015-01-07 23:45:29.025 1313 ERROR nova.compute.manager [req-cf035b15-008b-4f17-87a6-a53d1cef27c9 8fba366273ec429faaeb9548b14eaab8 9d70490f1dfe4b88bfab45f552a27e75] [instance: da048196-baf7-426c-9e06-ff1f6cd218eb] Instance failed to spawn
2015-01-07 23:45:29.071 1313 DEBUG nova.compute.manager [req-cf035b15-008b-4f17-87a6-a53d1cef27c9 8fba366273ec429faaeb9548b14eaab8 9d70490f1dfe4b88bfab45f552a27e75] [instance: da048196-baf7-426c-9e06-ff1f6cd218eb] Clean up resource before rescheduling. _reschedule_or_error /usr/lib/python2.7/site-packages/nova/compute/manager.py:1414
2015-01-07 23:45:29.076 1313 ERROR nova.virt.libvirt.driver [-] [instance: da048196-baf7-426c-9e06-ff1f6cd218eb] During wait destroy, instance disappeared.
2015-01-07 23:45:29.228 1313 DEBUG neutronclient.v2_0.client [-] Error message: 404 Not Found
2015-01-07 23:45:29.376 1313 ERROR nova.compute.manager [req-cf035b15-008b-4f17-87a6-a53d1cef27c9 8fba366273ec429faaeb9548b14eaab8 9d70490f1dfe4b88bfab45f552a27e75] [instance: da048196-baf7-426c-9e06-ff1f6cd218eb] Error: Unexpected vif_type=binding_failed
    ==========================================================================
    3 Node Configuration
    Controller Node ( 192.168.2.51) - MariaDB, Keystone, RabbitMQ, Swift, Cinder and Glance


Neutron node (192.168.2.53)
~~~~~~~~~~~~~~~~~~~~~~~

Note - sed -i 's,plugins/openvswitch/ovs_neutron_plugin.ini,plugin.ini,g' /etc/systemd/system/multi-user.target.wants/neutron-openvswitch-agent.service

1. neutron.conf:
grep ^[^#] /etc/neutron/neutron.conf
[DEFAULT]
[DEFAULT]
auth_strategy = keystone
rpc_backend = neutron.openstack.common.rpc.impl_kombu
rabbit_host = 192.168.2.51
rabbit_port = 5672
rabbit_userid = neutron
rabbit_password = neutron
core_plugin = ml2
service_plugins = router
force_gateway_on_subnet = True
notify_nova_on_port_status_changes = True
notify_nova_on_port_data_changes = True
nova_url = http://192.168.2.52:8774/v2
nova_admin_username = nova
nova_admin_tenant_name = services
nova_admin_password = nova
nova_admin_auth_url = http://192.168.2.51:35357/v2.0
[quotas]
[agent]
[keystone_authtoken]
auth_host = 192.168.2.51
admin_tenant_name = services
admin_user = neutron
admin_password = neutron
auth_uri = http://192.168.2.51:5000
auth_protocol = http
auth_port = 35357
[database]
connection = mysql://neutron:neutron@192.168.2.51/neutron_ml2
[service_providers]
service_provider=LOADBALANCER:Haproxy:neutron.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
service_provider=VPN:openswan:neutron.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Pradipta_OS_M
close date 2015-01-09 12:29:44.826548

Comments

AMQP server on 192.168.2.51:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 11 seconds.

Neutron needs to be able to connect to rabbitMQ. Is rabbit running on 192.168.2.51? Because as you can see, its not able to connect.

sfcloudman gravatar imagesfcloudman ( 2015-01-06 23:14:23 -0500 )edit

Hi Jacob, Sorry for the confusion,, It was old log,, Updated the correct log details. The issue is in nova log file (vif_type=binding_failed). I updated the correct driver in nova.conf file as per Openstack Guide. Please correct me if any parameter I missed in nova.conf file

Pradipta_OS_M gravatar imagePradipta_OS_M ( 2015-01-07 12:25:25 -0500 )edit

3 answers

Sort by ยป oldest newest most voted
0

answered 2015-01-09 12:29:21 -0500

The issue has been fixes. I did chages l3 and dhcp agent file on my neutron server.. Has created the tunnel in between Compute and Neutron and mapping the bridge communication. Thanks every for your support and advise.

== Nova instances ==
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| ID                                   | Name  | Status | Task State | Power State | Networks             |
+--------------------------------------+-------+--------+------------+-------------+----------------------+
| 221c786e-26a6-4435-b57e-fad66f1de89e | test1 | ACTIVE | -          | Running     | public=192.168.2.224 |
+--------------------------------------+-------+--------+------------+-------------+----------------------+
edit flag offensive delete link more

Comments

hiiii, pradipta can you please share what changes have you made..facing same problem.....

smcas gravatar imagesmcas ( 2015-09-02 07:37:18 -0500 )edit

Hi, it would be really helpful if you could post what changes you made to l3 and dhcp to get this working

davideagle gravatar imagedavideagle ( 2015-12-01 09:41:26 -0500 )edit
0

answered 2015-01-04 23:35:07 -0500

updated 2015-01-05 00:04:14 -0500

First of all, based on this :

/var/log/nova/nova-consoleauth.log

2015-01-04 15:04:10.355 3967 TRACE nova.openstack.common.threadgroup ProgrammingError: (ProgrammingError) (1146, "Table 'nova.services' doesn't exist") 'SELECT services.created_at AS services_created_at, services.updated_at AS services_updated_at, services.deleted_at AS services_deleted_at, services.deleted AS services_deleted, services.id AS services_id, services.host AS services_host, services.`binary` AS services_binary, services.topic AS services_topic, services.report_count AS services_report_count, services.disabled AS services_disabled, services.disabled_reason AS services_disabled_reason \nFROM services \nWHERE services.deleted = %s AND services.host = %s AND services.`binary` = %s \n LIMIT %s' (0, 'compute.labs.com', 'nova-consoleauth', 1)

You are missing tables in the DB. This indicates that nova-manage db sync was never run. You need to run this to create the proper tables/schema.

Run that and then try to spawn again to see what other errors emerge if any.

edit flag offensive delete link more

Comments

Thank you for the update, At the time of nova configuration I synch the nova db using requested command, and I cloud see the relevant table/schema populated nova db.. I re run the same command but still getting same error. Update error log in question. Please help me to fix this issue..

Pradipta_OS_M gravatar imagePradipta_OS_M ( 2015-01-05 00:24:58 -0500 )edit

I cloud see in DB all table are populated except the "Table 'nova.services'.. Kindly suggest

Pradipta_OS_M gravatar imagePradipta_OS_M ( 2015-01-05 00:26:30 -0500 )edit

The reason your VM is not launching is because Unexpected vif_type=binding_failed.

Are you using neutron or nova network?

The services table needs to be created when you run that command.

You MUST stop all nova services before running nova-manage db sync!!!!

sfcloudman gravatar imagesfcloudman ( 2015-01-05 00:48:51 -0500 )edit

I am using Neutron ML2 plugin with driver gre and mechanism_drivers openvswitch.. I stopped all nova active services for sync to nova db.. Can u pls suggest me how can I fix the error and let me know if I can share you any config details..

Pradipta_OS_M gravatar imagePradipta_OS_M ( 2015-01-05 03:12:16 -0500 )edit

Can you tail neutron server log and nova compute log during your spawn error.

sfcloudman gravatar imagesfcloudman ( 2015-01-05 23:44:05 -0500 )edit
0

answered 2015-01-06 00:11:20 -0500

Bipin gravatar image

Can you make sure the following is in your /etc/nova/nova.conf file of compute node ?

libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver (If not add it and restart the necessary services)

edit flag offensive delete link more

Comments

Bipin Thanks for your respond, I have updated above driver, but still getting same vif_type=binding_failed error. I have updated the config and log details in main,, Please have a look and suggest to me

Pradipta_OS_M gravatar imagePradipta_OS_M ( 2015-01-06 03:11:39 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2015-01-04 23:25:46 -0500

Seen: 4,025 times

Last updated: Jan 09 '15