Details
-
Bug
-
Status: Resolved
-
Resolution: Cannot Reproduce
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
6686
Description
Operations:
1. Setup 3 node ODL (feature: odl-ovsdb-openstack aka Legacy Netvirt)
2. Attempted failover in thie sequence
ODL1 down ODL2 up ODL3 up
ODL1 up, ODL2 down ODL3 up
--> Operations started to fail here
ODL1 up, ODL2 up, ODL3 up
--> no recovery
At this point ODL3 was listed as "owner" for all entities. All the operations were failing. Checking the logs in ODL2 and ODL3 indiciated a lot of blueprint errors and some WARN indicating problems with remoterpc
2016-09-09 21:48:21,009 | WARN | ult-dispatcher-2 | RpcRegistry | 168 - org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.Boron | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:packet:service?revision=2013-07-09)transmit-packet, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[
{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:92945849353687}]}
2016-09-09 21:48:21,009 | WARN | ult-dispatcher-2 | RpcRegistry | 168 - org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.Boron | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:packet:service?revision=2013-07-09)transmit-packet, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[
]}
2016-09-09 21:48:21,009 | WARN | ult-dispatcher-2 | RpcRegistry | 168 - org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.Boron | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:packet:service?revision=2013-07-09)transmit-packet, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[
]}