Uploaded image for project: 'ovsdb'
  1. ovsdb
  2. OVSDB-456

OVSDB CSIT regression. Operational store not showing expected data

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Highest Highest
    • Nitrogen-SR3
    • None
    • CSIT
    • None

      It seems recently that the carbon and nitrogen CSIT jobs for ovsdb have taken
      on a regression.

      these ones:
      https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-nitrogen/
      https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-carbon

      it does not appear that this regression is there in oxygen or flourine at the moment.

      one log message stood out to me:

      2018-03-12 02:50:25,786 | ERROR | on-dispatcher-87 | DataTreeChangeListenerActor      | 268 - org.opendaylight.controller.sal-clustering-commons - 1.6.3.SNAPSHOT | member-1-shard-topology-config: Error notifying listener org.opendaylight.ovsdb.southbound.OvsdbDataTreeChangeListener@7522fa0d
      java.lang.NullPointerException
      	at org.opendaylight.ovsdb.southbound.SouthboundMapper.suppressLocalIpPort(SouthboundMapper.java:381)[410:org.opendaylight.ovsdb.southbound-impl:1.5.3.SNAPSHOT]
      	at org.opendaylight.ovsdb.southbound.OvsdbConnectionManager.getInstanceIdentifier(OvsdbConnectionManager.java:279)[410:org.opendaylight.ovsdb.southbound-impl:1.5.3.SNAPSHOT]
      	at org.opendaylight.ovsdb.southbound.OvsdbDataTreeChangeListener.disconnect(OvsdbDataTreeChangeListener.java:145)[410:org.opendaylight.ovsdb.southbound-impl:1.5.3.SNAPSHOT]
      	at org.opendaylight.ovsdb.southbound.OvsdbDataTreeChangeListener.onDataTreeChanged(OvsdbDataTreeChangeListener.java:103)[410:org.opendaylight.ovsdb.southbound-impl:1.5.3.SNAPSHOT]
      	at org.opendaylight.controller.md.sal.binding.impl.BindingDOMDataTreeChangeListenerAdapter.onDataTreeChanged(BindingDOMDataTreeChangeListenerAdapter.java:41)[262:org.opendaylight.controller.sal-binding-broker-impl:1.6.3.SNAPSHOT]
      	at org.opendaylight.controller.cluster.datastore.DataTreeChangeListenerActor.dataChanged(DataTreeChangeListenerActor.java:67)[275:org.opendaylight.controller.sal-distributed-datastore:1.6.3.SNAPSHOT]
      	at org.opendaylight.controller.cluster.datastore.DataTreeChangeListenerActor.handleReceive(DataTreeChangeListenerActor.java:41)[275:org.opendaylight.controller.sal-distributed-datastore:1.6.3.SNAPSHOT]
      	at org.opendaylight.controller.cluster.common.actor.AbstractUntypedActor.onReceive(AbstractUntypedActor.java:38)[268:org.opendaylight.controller.sal-clustering-commons:1.6.3.SNAPSHOT]
      	at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:165)[37:com.typesafe.akka.actor:2.4.18]
      	at akka.actor.Actor$class.aroundReceive(Actor.scala:502)[37:com.typesafe.akka.actor:2.4.18]
      	at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:95)[37:com.typesafe.akka.actor:2.4.18]
      	at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)[37:com.typesafe.akka.actor:2.4.18]
      	at akka.actor.ActorCell.invoke(ActorCell.scala:495)[37:com.typesafe.akka.actor:2.4.18]
      	at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)[37:com.typesafe.akka.actor:2.4.18]
      	at akka.dispatch.Mailbox.run(Mailbox.scala:224)[37:com.typesafe.akka.actor:2.4.18]
      	at akka.dispatch.Mailbox.exec(Mailbox.scala:234)[37:com.typesafe.akka.actor:2.4.18]
      	at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)[484:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc]
      	at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)[484:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc]
      	at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)[484:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc]
      	at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)[484:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc]

      here's a specific job with it's associated karaf log file

            jluhrsen Jamo Luhrsen
            jluhrsen Jamo Luhrsen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: