-
Bug
-
Resolution: Done
-
None
-
Helium
-
None
-
Operating System: Linux
Platform: All
-
2523
Testbed:
Followed https://wiki.opendaylight.org/view/Running_and_testing_an_OpenDaylight_Cluster using cluster-deployer script to deploy a three node cluster. And set persistence to false as described in wiki. From accessing /jolokia/read/org.opendaylight.controller:Category=Shards,name=member-1-shard-inventory-config,type=DistributedConfigDatastore, can get the proper result as the wiki described. Also can see the three node have established tcp session with port 2550 to each other.
Configured one ASR9k to connect all the three controller IPs. And from controller side, can see the same switch info using restconf api from three nodes.
When try to deploy flow entries to device, the restconf returned 204 which means success, but no any flow mod messages sent from controller as packet capturing shown, so no flows can be seen in device.
Lots of errors like below can be found in karaf.log as attached, but don't know is it related to this issue.
2014-12-18 06:05:12,060 | ERROR | otification-1334 | NotifyTask | 217 - org.opendaylight.controller.sal-binding-broker-impl - 1.1.1.Helium-SR1 | Unhandled exception thrown by listener: org.opendaylight.controller.md.statistics.manager.impl.StatListenCommitFlow$$Broker$ListenerInvoker@6914364a