[OPNFLWPLUG-568] Li plugin: [Clustering]operation DS is not getting cleared in clustering stock odl even after disconnecting the ovs OF switch Created: 04/Nov/15  Updated: 27/Sep/21  Resolved: 21/Jul/16

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

Type: Bug
Reporter: Anpukarasi Muthukumaran Assignee: Kamal Rameshan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Other

Attachments: Text File karaf.log     HTML File operation_DS_log    
Issue Links:
Duplicate
duplicates OPNFLWPLUG-704 Operational Inventory data persists i... Resolved
External issue ID: 4576

 Description   

in clustering Stock odl testing, I observed that the operational DS is not getting cleared even after disconnecting the ovs OF switch.

I created 5 # node cluster test setup like c1,c2,c3,c4 and c5. and c1 is leader and others are follower. I have connected a ovs OF switch to C1 and checked the config and operational DS. Found that the connected OF switch details in operational DS. After sometime, I disconnected the OVS OF switch and confirmed that no OVS OF switch has connected with any of the cluster nodes. Then checked again the operational DS of either leader or follower , I am able to get the OVS OF switch information .

Step to recreate the issue:

1. create 5 # node cluster
2. connect a OVS OF switch to any one of cluster node
3. check the operational DS of the node using REST
4. wait for 5 mins and disconnect the switch from the cluster
5. again check the operational DS of the node using REST, still it is showing the ovs OF switch details. But the Port status of 6633 and 6653 are as follows;

root@mininet-vm:/home/anpu# netstat -an | grep 6633
tcp6 0 0 :::6633 :::* LISTEN

root@mininet-vm:/home/anpu# netstat -an | grep 6653
tcp6 0 0 :::6653 :::* LISTEN

The same status shown in all the cluster node.

Herewith I am enclosing the operational DS log when no active OVS OF switch connection

 Comments   
Comment by Anpukarasi Muthukumaran [ 04/Nov/15 ]

Attachment operation_DS_log has been added with description: operational DS log when no active OVS OF switch connection

Comment by Moiz Raja [ 17/Nov/15 ]

We need karaf logs which show if there are any exceptions.

Reassigning to ofplugin component for initial diagnosis.

Comment by Anpukarasi Muthukumaran [ 18/Nov/15 ]

Hi,

I have adding requested karaf.log for your reference.

Please let me know for further details

Thanks
Anpu

Comment by Anpukarasi Muthukumaran [ 18/Nov/15 ]

Attachment karaf.log has been added with description: karaf.log

Comment by Moiz Raja [ 18/Nov/15 ]

2015-11-18 04:39:04,787 | INFO | lt-dispatcher-18 | DeviceContextImpl | 280 - org.opendaylight.openflowplugin.impl - 0.1.2.Lithium-SR2 | Removing device from operational and closing transaction Manager for device:Uri [_value=openflow:1]
2015-11-18 04:39:04,787 | ERROR | lt-dispatcher-18 | EntityOwnershipListenerActor | 191 - org.opendaylight.controller.sal-distributed-datastore - 1.2.2.Lithium-SR2 | Error notifying listener org.opendaylight.openflowplugin.impl.role.OpenflowOwnershipListener@47042b4c
java.lang.NullPointerException
at org.opendaylight.openflowplugin.impl.device.TransactionChainManager.close(TransactionChainManager.java:177)[280:org.opendaylight.openflowplugin.impl:0.1.2.Lithium-SR2]
at org.opendaylight.openflowplugin.impl.device.DeviceContextImpl.onDeviceDisconnectedFromCluster(DeviceContextImpl.java:376)[280:org.opendaylight.openflowplugin.impl:0.1.2.Lithium-SR2]
at org.opendaylight.openflowplugin.impl.role.RoleContextImpl.onDeviceDisconnectedFromCluster(RoleContextImpl.java:155)[280:org.opendaylight.openflowplugin.impl:0.1.2.Lithium-SR2]
at org.opendaylight.openflowplugin.impl.role.OpenflowOwnershipListener.ownershipChanged(OpenflowOwnershipListener.java:56)[280:org.opendaylight.openflowplugin.impl:0.1.2.Lithium-SR2]
at org.opendaylight.controller.cluster.datastore.entityownership.EntityOwnershipListenerActor.onEntityOwnershipChanged(EntityOwnershipListenerActor.java:44)[191:org.opendaylight.controller.sal-distributed-datastore:1.2.2.Lithium-SR2]
at org.opendaylight.controller.cluster.datastore.entityownership.EntityOwnershipListenerActor.handleReceive(EntityOwnershipListenerActor.java:36)[191:org.opendaylight.controller.sal-distributed-datastore:1.2.2.Lithium-SR2]
at org.opendaylight.controller.cluster.common.actor.AbstractUntypedActor.onReceive(AbstractUntypedActor.java:34)[183:org.opendaylight.controller.sal-clustering-commons:1.2.2.Lithium-SR2]
at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:167)[176:com.typesafe.akka.actor:2.3.10]
at akka.actor.Actor$class.aroundReceive(Actor.scala:467)[176:com.typesafe.akka.actor:2.3.10]
at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:97)[176:com.typesafe.akka.actor:2.3.10]
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)[176:com.typesafe.akka.actor:2.3.10]
at akka.actor.ActorCell.invoke(ActorCell.scala:487)[176:com.typesafe.akka.actor:2.3.10]
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:254)[176:com.typesafe.akka.actor:2.3.10]
at akka.dispatch.Mailbox.run(Mailbox.scala:221)[176:com.typesafe.akka.actor:2.3.10]
at akka.dispatch.Mailbox.exec(Mailbox.scala:231)[176:com.typesafe.akka.actor:2.3.10]
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)[173:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)[173:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)[173:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)[173:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)[173:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]

Comment by Kamal Rameshan [ 18/Nov/15 ]

Hi,

Can you tell us which openflowplugin version you have been using? Is it from stable-lithium or Master?

The exception looks like the one fixed in this patch:
https://git.opendaylight.org/gerrit/#/c/28977/

This patch couldn't make it to stable-lithium SR2, but the latest of both stable-lithium and master should have it.

Comment by Abhijit Kumbhare [ 30/Jan/16 ]

I am reducing the severity of this issue to "normal" - since there has been no response since November. If still an issue - please increase back the severity.

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