[OPNFLWPLUG-943] Secondary Controllers are not able to take mastership when primary controller goes down Created: 12/Sep/17  Updated: 27/Sep/21  Resolved: 06/Feb/18

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Mayank Aggarwal Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC


External issue ID: 9146

 Description   

I am running ODL in 3 node cluster with 50 switches linear topology out of which most of switches master is member-1, when I killed this controller I got exception similar to mentioned in this URL https://www.mail-archive.com/openflowplugin-dev@lists.opendaylight.org/msg01287.html# on controller which is trying to take mastership of switches. I also verified in opendaylight-inventory:nodes and network-topology datastores and the switches for which I am getting these exceptions are not present there. I am using carbon SR1 distribution, OVS version 2.5.0 with mininet.

I also checked in ovs-vsctl show and switches are shown connected to the controllers. The exceptions that i got are

2017-09-12 15:06:13,224 | ERROR | CommitFutures-5 | TransactionChainManager | 220 - org.opendaylight.openflowplugin.impl - 0.4.1.Carbon | Transaction commit failed.
TransactionCommitFailedException{message=Data did not pass validation., errorList=[RpcError [message=Data did not pass validation., severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[

{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:42}

] does not exist. Cannot apply modification to its children.]]}



 Comments   
Comment by Anil Vishnoi [ 12/Dec/17 ]

mayank.agarwal@aricent.com do you have full karaf log from the issue. There is a known issue in OVS 2.5.0 as well, where it does not show the correct role for the controller. For that you will have to upgrade to the OVS 2.8.1 version.

Comment by Anil Vishnoi [ 06/Feb/18 ]

Closing this bug due to inactivity. Please re-open the bug if you hit the issue again and can provide all the required logs.

Generated at Wed Feb 07 20:33:48 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.