[VTN-145] Issue in 3-Node cluster formation Created: 12/Sep/16  Updated: 19/Oct/17  Resolved: 13/Sep/16

Status: Resolved
Project: vtn
Component/s: VTN Manager
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: YOGA LAKSHMI SWETHA PAYYAVULA Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6694

 Description   

Issue: unable to form the 3-node cluster.

Scenario: When the cluster is configured with 3 node using Boron RC2 distribution, the cluster formation fails. The nodes are not reachable to each other. PFB for the logs:

Received UnreachableMember: memberName MemberName

{name=member-1}

, address: akka.tcp://opendaylight-cluster-data@10.106.138.191:2550
2016-09-09 21:31:47,943 | INFO | lt-dispatcher-16 | ShardManager | 193 - org.opendaylight.controller.sal-distributed-datastore - 1.4.0.Boron-RC2 |
Received UnreachableMember: memberName MemberName

{name=member-2}

, address: akka.tcp://opendaylight-cluster-data@10.106.138.118:2550
2016-09-09 21:32:06,996 | INFO | ult-dispatcher-3 | kka://opendaylight-cluster-data) | 177 - com.typesafe.akka.slf4j - 2.4.7 | Cluster Node
[akka.tcp://opendaylight-cluster-data@10.106.138.160:2550] - Leader can currently not perform its duties, reachability status:
[akka.tcp://opendaylight-cluster-data@10.106.138.118:2550 -> akka.tcp://opendaylight-cluster-data@10.106.138.191:2550: Unreachable [Unreachable] (1),
akka.tcp://opendaylight-cluster-data@10.106.138.191:2550 -> akka.tcp://opendaylight-cluster-data@10.106.138.118:2550: Unreachable [Unreachable] (1)],
member status: [akka.tcp://opendaylight-cluster-data@10.106.138.118:2550 Up seen=false, akka.tcp://opendaylight-cluster-data@10.106.138.160:2550 Up seen=true,
akka.tcp://opendaylight-cluster-data@10.106.138.191:2550 Up seen=false]
2016-09-09 21:32:28,039 | INFO | config-pusher | ConfigPusherImpl

132 - org.opendaylight.controller.config-persister-impl - 0.5.0.Boron-RC2 Successfully pushed configuration snapshot 00-netty.xml(odl-restconf,odl-restconf)


 Comments   
Comment by YOGA LAKSHMI SWETHA PAYYAVULA [ 12/Sep/16 ]

[root@localhost data]# python /root/cluster.py
****Cluster Tests*****
Please enter ipaddress to find Leader Node : 10.106.138.252
you entered 10.106.138.252

=================== Leader Node ======================

10.106.138.252-Up

=================== Follower Node =====================

[]

=================== Entity Details ===================

NODE ID = openflow:103525727201345
OWNER = member-1
IP Address = 10.106.138.252
NODE ID = vtn:inventory
OWNER = member-1
IP Address = 10.106.138.252
NODE ID = openflow:103525727201345
OWNER = member-1
IP Address = 10.106.138.252
NODE ID = vtn:config
OWNER = member-1
IP Address = 10.106.138.252
NODE ID = vBridge:vtn1/vbr1
OWNER = member-1
IP Address = 10.106.138.252
NODE ID = vtn:flow-stats
OWNER = member-1
IP Address = 10.106.138.252

The remaining follower nodes are not added dues to the below failure

Comment by YOGA LAKSHMI SWETHA PAYYAVULA [ 13/Sep/16 ]

This bug is invalid, This issue occured due to some internal issues, which has been resolved now.

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