Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

ph0tek, sorry for the slow response, but just now able to take a look at your karaf.log and packet capture.

firstly, are you polling ODL with REST calls while it's coming up? If so, that would explain the many exceptions in WebAppPublisher while authentication is coming online. This is expected. However, if you are not polling it, that is something curious to debug, although probably not related to this problem.

secondly, I saw this:

ERROR - org.opendaylight.ovsdb.northbound
org.osgi.framework.BundleException: The bundle "org.opendaylight.ovsdb.northbound_0.7.1.Lithium-SR1 [423]" could not be resolved. Reason: Missing Constraint: Import-Package: org.opendaylight.ovsdb.plugin.api; version="[1.1.0,2.0.0)"

do you have any idea about that?

next, I saw this:

ERROR | ntLoopGroup-10-1 | ExecutionList                    | 64 - com.google.guava - 18.0.0 | RuntimeException while executing runnable com.google.common.util.concurrent.Futures$6@74dd028f with executor INSTANCE
java.lang.IllegalStateException: registered session context is invalid
at org.opendaylight.openflowplugin.openflow.md.core.session.OFSessionUtil.registerSession(OFSessionUtil.java:99)[269:org.opendaylight.openflowplugin:0.1.1.Lithium-SR1]
.
<snip>
.

this looks like some trouble with something openflow trying to establish a session. I know this is at a timestamp before you noted that pica8 connected (12:17:02,556 -vs- 12:17:58,177), but something is having trouble.

You do have a lot of features installed. Maybe there is some conflict happening. How are you installing the features? Can you give those details?

Also could you try connecting just the pica8 switch after only installing odl-ovsdb-southbound-impl-rest? This will not bring in any openflow, but it will be another good data point to know if it works or not.

I did not look at the packet capture too deeply yet.