Manu, maybe check what a packet capture tells you.
also, try a full reset of the ovs node. some steps I usually take are like this in our CSIT code: https://github.com/opendaylight/integration-test/blob/master/csit/libraries/OVSDB.robot#L128-L131 then reconnect things. if things are healthy on the ODL side, netvirt will recreate your br-int just throwing out ideas for now. something seems broken. and, no, I don't think this is any known issue with Carbon SR2. JamO On 11/20/2017 06:25 PM, [email protected] wrote: > Hello > > > I am working on integrating ODL Carbon SR2 and OpenStack Pike for OPNFV. > After deploying, I can not create VM, nova log said > neutron timed out. So I checked openvswitch log and found the following > reconnection seems to be the source of the issue: > > > 2017-11-20T17:08:47.539Z|00058|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connected > > 2017-11-20T17:08:47.541Z|00059|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connection > closed by peer > > 2017-11-20T17:08:55.538Z|00060|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connected > > 2017-11-20T17:08:55.540Z|00061|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connection > closed by peer > > 2017-11-20T17:09:03.537Z|00062|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connected > > 2017-11-20T17:09:03.539Z|00063|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connection > closed by peer > > 2017-11-20T17:09:11.538Z|00064|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connected > > 2017-11-20T17:09:11.540Z|00065|rconn|INFO|br-int<->tcp:192.168.1.105:6653:connection > closed by peer > > > In the same time, karaf.log shows the following errors: > > > 2017-11-21 01:30:55,535 | INFO | ntLoopGroup-7-33 | ContextChainHolderImpl > | 330 - > org.opendaylight.openflowplugin.impl - 0.4.2.Carbon | Device > openflow:206853503483370 connected. > > 2017-11-21 01:30:55,535 | WARN | ntLoopGroup-7-33 | ContextChainHolderImpl > | 330 - > org.opendaylight.openflowplugin.impl - 0.4.2.Carbon | Device > openflow:206853503483370 is already trying to connect, wait > until succeeded or disconnected. > > 2017-11-21 01:31:03,534 | INFO | ntLoopGroup-7-34 | ConnectionAdapterImpl > | 319 - > org.opendaylight.openflowjava.openflow-protocol-impl - 0.9.2.Carbon | Hello > received > > 2017-11-21 01:31:03,535 | INFO | ntLoopGroup-7-34 | ContextChainHolderImpl > | 330 - > org.opendaylight.openflowplugin.impl - 0.4.2.Carbon | Device > openflow:206853503483370 connected. > > 2017-11-21 01:31:03,535 | WARN | ntLoopGroup-7-34 | ContextChainHolderImpl > | 330 - > org.opendaylight.openflowplugin.impl - 0.4.2.Carbon | Device > openflow:206853503483370 is already trying to connect, wait > until succeeded or disconnected. > > 2017-11-21 01:31:11,534 | INFO | ntLoopGroup-7-35 | ConnectionAdapterImpl > | 319 - > org.opendaylight.openflowjava.openflow-protocol-impl - 0.9.2.Carbon | Hello > received > > 2017-11-21 01:31:11,535 | INFO | ntLoopGroup-7-35 | ContextChainHolderImpl > | 330 - > org.opendaylight.openflowplugin.impl - 0.4.2.Carbon | Device > openflow:206853503483370 connected. > > 2017-11-21 01:31:11,535 | WARN | ntLoopGroup-7-35 | ContextChainHolderImpl > | 330 - > org.opendaylight.openflowplugin.impl - 0.4.2.Carbon | Device > openflow:206853503483370 is already trying to connect, wait > until succeeded or disconnected. > > > I am new to openflowplugin module, so please guide me on how to debug this > kind of re-connenct problem. Or is it a issue > already known? > > > Manu thanks! > > > > > B. R., > > Zhijiang > > > > _______________________________________________ > openflowplugin-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > _______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
