Ask Your Question
0

No able to create an instance in odl integrated RDO Kilo openstack

asked 2015-10-26 10:23:34 -0500

kuldeep_verma gravatar image

updated 2016-02-04 02:49:55 -0500

I have 2 node architecture set up of RDO Kilo OpenStack and I have integareted it with OpenDayLight Helium SR4. I am following this link : https://wiki.opendaylight.org/view/OpenStack_and_OpenDaylight. Feature installed on odl are:

odl-base-all odl-aaa-authn odl-restconf odl-nsf-all odl-adsal-northbound odl-mdsal-apidocs odl-ovsdb-openstack odl-ovsdb-northbound odl-dlux-core

My teanant network type is VXLAN. I can see two node connected in dlux GUI. ovs-vsctl show on controller and compute node shows that odl is connected. But I am facing the issue while creating an instance. I am getting error as no valid host found. I searched the forum but none of the post matches my problem.

NEUTRON SERVER LOG says :

2015-10-26 14:02:37.442 4315 ERROR neutron.plugins.ml2.managers [req-bdcbc200-64a2-4925-8157-112abbbddeab ] Failed to bind port 93147fb7-bd07-4ff9-a14f-24a5bff4eb9d on host compute
2015-10-26 14:02:37.443 4315 ERROR neutron.plugins.ml2.managers [req-bdcbc200-64a2-4925-8157-112abbbddeab ] Failed to bind port 93147fb7-bd07-4ff9-a14f-24a5bff4eb9d on host compute

NOVA COMPUTE LOG on COMPUTE NODE :

2015-10-26 14:02:49.226 2472 TRACE nova.compute.manager [instance: ec335d51-5e07-4493-9c95-1eac9372d2ed]     _("Unexpected vif_type=%s") % vif_type)
2015-10-26 14:02:49.226 2472 TRACE nova.compute.manager [instance: ec335d51-5e07-4493-9c95-1eac9372d2ed] NovaException: Unexpected vif_type=binding_failed

Thanks in advance !! With Regards, Kuldeep

edit retag flag offensive close merge delete

Comments

Can you paste an ovs-vsctl show in both nodes?

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2016-02-04 03:04:40 -0500 )edit

Are you seeing any exceptions in the karaf logs? If so, can you paste the error logs? On the other hand, ODL Beryllium release has lot of fixes and is more stable version compared to Helium. If Helium release is not a must, you can consider giving a try with Beryllium release.

sridhargaddam gravatar imagesridhargaddam ( 2016-03-31 05:49:41 -0500 )edit

Agree with @sridhargaddam . helium is too many bugs, most of the related with l3 routing to external networks

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2016-03-31 12:01:00 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-03-29 07:09:09 -0500

ihar-hrachyshka gravatar image

Could you please enable debug=true for neutron-server and repeat? Are there any more details above the error message you quoted that suggest why the host failed to bind the port?

edit flag offensive delete link more

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-10-26 10:23:34 -0500

Seen: 430 times

Last updated: Mar 29 '16