[OVSDB-349] Cannot create QOS entry when OVS instance is the connection initiator Beryllium-SR1,-SR2 Created: 23/Jun/16  Updated: 19/Oct/17  Resolved: 28/Jun/16

Status: Resolved
Project: ovsdb
Component/s: Southbound.Open_vSwitch
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Ibrahim Abdelghany Assignee: Unassigned
Resolution: Done 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: 6103

 Description   

After sending the below request, adding an already existing OVS instance to the config tree, the error from karaf (below the request) appears. This exception does not happen if the controller is the connection initiator. Moreover this error is repeated whenever a QOS entry or a QUEUE entry is added to the config tree under the OVS node.

It appears that QOS and QUEUEs cannot be configured unless the controller is the connection initiator.

PUT /restconf/config/network-topology:network-topology/topology/ovsdb:1/node/ovsdb%3A%2F%2Fuuid%2F2c7ecb6c-41b1-4e6a-9ef9-6c98f0768400 HTTP/1.1
Host: localhost:8181
Content-Type: application/json
Cache-Control: no-cache
Postman-Token: 332e6e95-850e-be1a-98f4-68eeeb8a40f2

{
"node":

{ "node-id": "ovsdb://uuid/2c7ecb6c-41b1-4e6a-9ef9-6c98f0768400" }

}

2016-06-23 12:07:27,069 | ERROR | on-dispatcher-38 | DataChangeListener | 291 - org.opendaylight.controller.sal-distributed-datastore - 1.3.1.Beryllium-SR1 | Error notifying listener org.opendaylight.ovsdb.southbound.OvsdbDataChangeListener
java.lang.NullPointerException
at org.opendaylight.ovsdb.southbound.OvsdbDataChangeListener.connectionInstancesFromMap(OvsdbDataChangeListener.java:207)[299:org.opendaylight.ovsdb.southbound-impl:1.2.2.Beryllium-SR1]
at org.opendaylight.ovsdb.southbound.OvsdbDataChangeListener.connectionInstancesFromChanges(OvsdbDataChangeListener.java:180)[299:org.opendaylight.ovsdb.southbound-impl:1.2.2.Beryllium-SR1]
at org.opendaylight.ovsdb.southbound.OvsdbDataChangeListener.updateData(OvsdbDataChangeListener.java:95)[299:org.opendaylight.ovsdb.southbound-impl:1.2.2.Beryllium-SR1]
at org.opendaylight.ovsdb.southbound.OvsdbDataChangeListener.onDataChanged(OvsdbDataChangeListener.java:82)[299:org.opendaylight.ovsdb.southbound-impl:1.2.2.Beryllium-SR1]
at org.opendaylight.controller.md.sal.binding.impl.AbstractForwardedDataBroker$TranslatingDataChangeInvoker.onDataChanged(AbstractForwardedDataBroker.java:143)[266:org.opendaylight.controller.sal-binding-broker-impl:1.3.1.Beryllium-SR1]
at org.opendaylight.controller.cluster.datastore.DataChangeListener.dataChanged(DataChangeListener.java:66)[291:org.opendaylight.controller.sal-distributed-datastore:1.3.1.Beryllium-SR1]
at org.opendaylight.controller.cluster.datastore.DataChangeListener.handleReceive(DataChangeListener.java:39)[291:org.opendaylight.controller.sal-distributed-datastore:1.3.1.Beryllium-SR1]
at org.opendaylight.controller.cluster.common.actor.AbstractUntypedActor.onReceive(AbstractUntypedActor.java:34)[287:org.opendaylight.controller.sal-clustering-commons:1.3.1.Beryllium-SR1]
at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:167)[276:com.typesafe.akka.actor:2.3.14]
at akka.actor.Actor$class.aroundReceive(Actor.scala:467)[276:com.typesafe.akka.actor:2.3.14]
at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:97)[276:com.typesafe.akka.actor:2.3.14]
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)[276:com.typesafe.akka.actor:2.3.14]
at akka.actor.ActorCell.invoke(ActorCell.scala:487)[276:com.typesafe.akka.actor:2.3.14]
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)[276:com.typesafe.akka.actor:2.3.14]
at akka.dispatch.Mailbox.run(Mailbox.scala:220)[276:com.typesafe.akka.actor:2.3.14]
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)[276:com.typesafe.akka.actor:2.3.14]
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)[273:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c]
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)[273:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c]
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)[273:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c]
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)[273:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c]



 Comments   
Comment by Sam Hague [ 23/Jun/16 ]

Adding Eric. Eric, did you rework this in the last patches for QoS/Queue?

Comment by Eric Multanen [ 23/Jun/16 ]

Sounds like this could be related to OVSDB-337. But don't think that fix made it into SR1 (not sure about SR2 either)

Comment by Anil Vishnoi [ 23/Jun/16 ]

Patch for OVSDB-337 is merged after SR2, so it's part of the latest stable/beryllium branch and will be part of SR3. Ibrahim, can you please test it against the latest stable/beryllium branch and confirm if you see the same issue.

Comment by Anil Vishnoi [ 28/Jun/16 ]

This issue seems to be resolved in latest stable/beryllium branch. I am closing this bug, but if you still see the bug, please re-open the bug.

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