Hi,
When I am executing the following commands in 3-node clusters, the internal and
external bridge dump flows are not created.
The below steps were followed,
1. 3- Node clusters is Up.
2. Clearing the OVS instance.
3. Adding external bridge and set-manager
4. Verified that the default dump flows are created properly.
5. sudo systemctl stop openvswitch;sudo systemctl start openvswitch;sudo
ovs-vsctl show; - Executed more than 1 times as it is.
6. Verified that dump flows are not available.
I had verified the karaf logs and found the following timed out exception, due
to that cluster new role is not properly setting.
2017-01-16 20:00:37,516 | WARN | lt-dispatcher-26 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:37,525 | WARN | lt-dispatcher-26 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:37,545 | WARN | lt-dispatcher-25 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:37,555 | WARN | lt-dispatcher-26 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:37,575 | WARN | lt-dispatcher-25 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:37,584 | WARN | lt-dispatcher-15 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:37,595 | WARN | lt-dispatcher-15 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:37,605 | WARN | lt-dispatcher-15 | RpcRegistry
| 192 - org.opendaylight.controller.sal-remoterpc-connector -
1.4.2.Boron-SR2 | Timed out finding routers for
RouteIdentifierImpl{context=null,
type=(urn:opendaylight:flow:service?revision=2013-08-19)update-flow,
route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:127589286723234}]}
2017-01-16 20:00:42,315 | WARN | pool-33-thread-1 | DeviceContextImpl
| 299 - org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 | New role
BECOMESLAVE was not propagated to device openflow:127589286723234 during 10 sec
2017-01-16 20:00:42,316 | ERROR | pool-33-thread-1 | SalRoleServiceImpl
| 299 - org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 |
SetRoleService set Role BECOMESLAVE for Node:
KeyedInstanceIdentifier{targetType=interface
org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node,
path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes,
org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey
[_id=Uri [_value=openflow:127589286723234]]]]} fail . Reason
java.util.concurrent.CancellationException: Task was cancelled.
2017-01-16 20:00:42,316 | WARN | pool-33-thread-1 | DeviceManagerImpl
| 299 - org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 | Was not
able to set role SLAVE to device on node openflow:127589286723234
I have seen the following patch has implemented timed out exception while
retries and wait for routed RPCs.
https://git.opendaylight.org/gerrit/#/c/35306/
and for avoiding the above exception do we increase GOSSIP interval time?.
Please share your input on this.
Regards,
Vinoth
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction,
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and
other defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
