Ask Your Question
0

ERROR problme Mechanism driver 'opendaylight' failed in create_network_postcommit

asked 2015-02-15 16:42:06 -0700

sunday gravatar image

Hello. I new to OpenDaylight controler.

I have set up an OpenStack (Juno) configuration: 1 x Control node 1 x Network node 2 x Compute nodes 1 x SDN Controller node (OpenDayLight 0.2.2-Helium-SR2)

I have gone throw the guide https://wiki.opendaylight.org/view/OpenStackandOpenDaylight and setup my SDN envirement but when I try to create a network with the neutron I get:

neutron net-create private Internal Server Error (HTTP 500) (Request-ID: req-63d2ff2d-d49c-4f31-983f-cc66aed3a1e1)

in my log /var/log/neutron/server.log i get an error:

2015-02-16 01:37:09.434 25935 ERROR neutron.plugins.ml2.managers [req-63d2ff2d-d49c-4f31-983f-cc66aed3a1e1 None] Mechanism driver 'opendaylight' failed in createnetworkpostcommit 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers Traceback (most recent call last): 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/managers.py", line 291, in callondrivers 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers getattr(driver.obj, methodname)(context) 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/mechanismodl.py", line 145, in createnetworkpostcommit 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers self.synchronize('create', ODLNETWORKS, context) 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/mechanismodl.py", line 174, in synchronize 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers self.syncfull(context) 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/openstack/common/lockutils.py", line 249, in inner 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers return f(args, *kwargs) 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/mechanismodl.py", line 233, in syncfull 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers self.syncresources(collectionname, context) 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/mechanismodl.py", line 221, in syncresources 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers self.sendjson('post', collectionname, {key: tobesynced}) 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/mechanismodl.py", line 299, in sendjson 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers r.raiseforstatus() 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/requests/models.py", line 795, in raiseforstatus 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers raise HTTPError(httperrormsg, response=self) 2015-02-16 01:37:09.434 25935 TRACE neutron.plugins.ml2.managers HTTPError: 500 Server Error: Internal ... (more)

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2015-02-16 00:55:25 -0700

Vishal Thapar gravatar image

I normally run into this error when Neutron is unable to reach ODL server. You can try the following:

  1. Is ODL listening on port 8080? Run netstat to confirm.
  2. Are you able to reach ODL node's port 8080 form your Neutron Server node? Try 'wget <odl-ip>:8080' and see if you get any response. If you're using a proxy, try the same again with '--no-proxy' option. If second one works, then you need to add ODL ip to your no-proxy list on neutron server node.</odl-ip>
  3. Check your ODL, if it is still running or any exceptions in log. With hydrogen I would sometimes get into "Out-of-memory" error on receiving requests from Neutron.

Neutron server node refers to wherever you're running Neutron server. Most folks run it on controller node but I've seen some installations run it on Network node also.

edit flag offensive delete publish link more
0

answered 2015-02-17 10:10:42 -0700

sunday gravatar image
  1. The port 8080 is opened (IPtables and selinux disabled) [root@opendaylight ~]# lsof -i -nP | grep 8080 java 19922 root 98u IPv6 138372 0t0 TCP *:8080 (LISTEN)

  2. I used curl trigger a HTTP request [root@openstack01 ~]# curl -u admin:admin http://<odl-ip>:8080/controller/nb/v2/neutron/networks { "networks" : [ ] }</odl-ip>

another test is: curl -u admin:admin http://10.9.99.44:8080/controller/nb/v2/neutron <title>Apache Tomcat/7.0.53 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style>

HTTP Status 404 - Not Found


type Status report

message Not Found

description The requested resource is not available.


Apache Tomcat/7.0.53

  1. I am using Helium ODL and still get the same error.

ERROR neutron.plugins.ml2.managers [req-b0414c73-f1d5-454a-81ab-252873531307 None] Mechanism driver 'opendaylight' failed in createnetworkpostcommit

I am running neutron server on my control node. I put the neutron server in the debug mode and still didn't find any clue of why I am getting the upper error.

edit flag offensive delete publish link more

Comments

What features did you load up in OpenDaylight "feature:list -i" at the karaf console.

Chris O'Shea ( 2015-02-17 11:54:33 -0700 )edit

odl-restconf,odl-restconf-noauth,odl-mdsal-apidocs,standard,config,package,http,war,kar,ssh,management,odl-protocol-framework,odl-config-persister,odl-config-startup,odl-l2switch-switch,odl-l2switch-hosttracker,odl-l2switch-addresstracker,odl-l2switch-arphandler,odl-l2switch-loopremover,odl-l2switch-packethandler,odl-mdsal-broker,odl-adsal-all,odl-adsal-core,odl-adsal-networkconfiguration,odl-adsal-connection,odl-adsal-clustering,odl-adsal-configuration,odl-adsal-thirdparty,

sunday ( 2015-02-17 15:04:53 -0700 )edit

odl-ovsdb-library,odl-ovsdb-schema-openvswitch,odl-ovsdb-schema-hardwarevtep,odl-ovsdb-plugin,odl-ovsdb-northbound,odl-ovsdb-openstack,odl-openflowjava-protocol,odl-yangtools-models,odl-yangtools-data-binding,odl-yangtools-binding,odl-yangtools-common,odl-yangtools-binding-generator,odl-config-netty,odl-dlux-core,odl-mdsal-common,odl-config-api,odl-config-netty-config-api,odl-config-core,odl-config-manager,odl-nsf-all,odl-nsf-managers,odl-adsal-northbound,odl-adsal-compatibility,odl-flow-model,odl-flow-services,tran

sunday ( 2015-02-17 15:04:56 -0700 )edit

Quit a lot of modules :) .... I hope that is not a problem ???

sunday ( 2015-02-17 15:05:49 -0700 )edit

It could be some of these module don't work well with each other. such as L2switch, i recommend only installed the needed ones for ovsdb neutron. I also don't see neutron as a feature being installed.

Chris O'Shea ( 2015-02-17 17:41:10 -0700 )edit
0

answered 2016-02-22 08:30:56 -0700

subhasis777 gravatar image

I am getting this issue please some body answer. openstack@openstack-1:~/devstack$ /usr/local/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2conf.ini Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future. 2016-02-22 21:37:39.105 INFO neutron.common.config [-] Logging enabled! 2016-02-22 21:37:39.105 INFO neutron.common.config [-] /usr/local/bin/neutron-server version 7.0.4.dev19 2016-02-22 21:37:39.106 DEBUG neutron.common.config [-] command line: /usr/local/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2conf.ini from (pid=18184) setuplogging /opt/stack/neutron/neutron/common/config.py:219 2016-02-22 21:37:39.107 INFO neutron.common.config [-] Logging enabled! 2016-02-22 21:37:39.108 INFO neutron.common.config [-] /usr/local/bin/neutron-server version 7.0.4.dev19 2016-02-22 21:37:39.108 DEBUG neutron.common.config [-] command line: /usr/local/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2conf.ini from (pid=18184) setuplogging /opt/stack/neutron/neutron/common/config.py:219 2016-02-22 21:37:39.109 INFO neutron.common.config [-] Config paste file: /etc/neutron/api-paste.ini 2016-02-22 21:37:39.120 DEBUG osloconcurrency.lockutils [-] Lock "manager" acquired by "neutron.manager.createinstance" :: waited 0.000s from (pid=18184) inner /usr/local/lib/python2.7/dist-packages/osloconcurrency/lockutils.py:270 2016-02-22 21:37:39.121 INFO neutron.manager [-] Loading core plugin: neutron.plugins.ml2.plugin.Ml2Plugin 2016-02-22 21:37:39.253 DEBUG neutron.quota.resourceregistry [-] Tracking information for resource: subnet configured from (pid=18184) settrackedresource /opt/stack/neutron/neutron/quota/resourceregistry.py:199 2016-02-22 21:37:39.253 DEBUG neutron.quota.resourceregistry [-] Tracking information for resource: network configured from (pid=18184) settrackedresource /opt/stack/neutron/neutron/quota/resourceregistry.py:199 2016-02-22 21:37:39.254 DEBUG neutron.quota.resourceregistry [-] Tracking information for resource: subnetpool configured from (pid=18184) settrackedresource /opt/stack/neutron/neutron/quota/resourceregistry.py:199 2016-02-22 21:37:39.254 DEBUG neutron.quota.resourceregistry [-] Tracking information for resource: securitygrouprule configured from (pid=18184) settrackedresource /opt/stack/neutron/neutron/quota/resourceregistry.py:199 2016-02-22 21:37:39.255 DEBUG neutron.quota.resourceregistry [-] Tracking information for resource: securitygroup configured from (pid=18184) settrackedresource /opt/stack/neutron/neutron/quota/resourceregistry.py:199 2016-02-22 21:37:39.255 DEBUG neutron.quota.resourceregistry [-] Tracking information for resource: port configured from (pid=18184) settrackedresource /opt/stack/neutron/neutron/quota/resourceregistry.py:199 2016-02-22 21:37:39.256 INFO neutron.plugins.ml2.managers [-] Configured type driver names: ['local'] 2016-02-22 21:37:39.258 INFO neutron.plugins.ml2.drivers.typelocal [-] ML2 LocalTypeDriver initialization complete 2016-02-22 21:37:39.259 INFO neutron.plugins.ml2.managers [-] Loaded type driver names: ['local'] 2016-02-22 21:37:39.260 INFO neutron.plugins.ml2.managers [-] Registered ... (more)

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
2 followers

Stats

Asked: 2015-02-15 16:42:06 -0700

Seen: 2,258 times

Last updated: Feb 22 '16