https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-206 netvirt <p>Steps to reproduce in a 3 node cluster:</p> <p>Used stable/bo.</p> <p>Used ODL 3 node (feature: odl-ovsdb-openstack)</p> <p>2 Openstack nodes, 1 control and 1 compute node</p> <p>1.create a network1.</p> <p>Below are steps of restart OVS on Control Node. </p> <p>2.Stop OVS with the following command. <br/> 　systemctl stop openvswitch </p> <p>3.Check ODL log to confirm that processing of OVS stop are finished. </p> <p>4.Start OVS with the following command. <br/> 　systemctl start openvswitch </p> <p>Now checked the flows, but flows are not existed. <br/> Out of 3 attempts we can able to reproduce one time.</p> <p>Used following distribution when we faced this issue</p> <p><a href="https://nexus.opendaylight.org/content/groups/public/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/distribution-karaf-0.5.0-Boron.tar.gz" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/groups/public/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/distribution-karaf-0.5.0-Boron.tar.gz</a></p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-206

Flows do not exists after OVS restarted on Controller Node and Compute Node.

Bug Resolved Done Bertrand Low Karthikeyan Mon, 17 Oct 2016 09:28:56 +0000 Fri, 9 Mar 2018 18:21:31 +0000 Mon, 5 Dec 2016 09:21:45 +0000 Boron 0 5 <p>Attachment ODL1.zip has been added with description: karaf logs for odl1.</p> <p>Attachment ODL2.zip has been added with description: karaf logs for odl2.</p> <p>Attachment ODL3.zip has been added with description: karaf logs for odl3</p> <p>ModifiedNodeDoesNotExistException occurred,</p> <p>2016-10-14 15:20:55,598 | WARN | ult-dispatcher-4 | ShardDataTree | 193 - org.opendaylight.controller.sal-distributed-datastore - 1.4.0.Boron | member-1-shard-inventory-config: Store Tx member-1-datastore-config-fe-0-txn-476: Data validation failed for path /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:97626771813463} <p>].<br/> org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:97626771813463} <p>] does not exist. Cannot apply modification to its children.<br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:281)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkChildPreconditions(AbstractNodeContainerModificationStrategy.java:305)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:288)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.MinMaxElementsValidation.checkTouchApplicable(MinMaxElementsValidation.java:106)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkChildPreconditions(AbstractNodeContainerModificationStrategy.java:305)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:288)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.StructuralContainerModificationStrategy.checkApplicable(StructuralContainerModificationStrategy.java:99)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkChildPreconditions(AbstractNodeContainerModificationStrategy.java:305)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:288)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.RootModificationApplyOperation.checkApplicable(RootModificationApplyOperation.java:72)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractDataTreeTip.validate(AbstractDataTreeTip.java:37)<span class="error">&#91;81:org.opendaylight.yangtools.yang-data-impl:1.0.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.ShardDataTree.processNextTransaction(ShardDataTree.java:524)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.ShardDataTree.startCanCommit(ShardDataTree.java:560)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.SimpleShardDataTreeCohort.canCommit(SimpleShardDataTreeCohort.java:81)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.CohortEntry.canCommit(CohortEntry.java:98)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.handleCanCommit(ShardCommitCoordinator.java:237)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.handleReadyLocalTransaction(ShardCommitCoordinator.java:201)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.Shard.handleReadyLocalTransaction(Shard.java:433)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.datastore.Shard.handleNonRaftCommand(Shard.java:239)<span class="error">&#91;193:org.opendaylight.controller.sal-distributed-datastore:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.raft.RaftActor.handleCommand(RaftActor.java:291)<span class="error">&#91;189:org.opendaylight.controller.sal-akka-raft:1.4.0.Boron&#93;</span><br/> at org.opendaylight.controller.cluster.common.actor.AbstractUntypedPersistentActor.onReceiveCommand(AbstractUntypedPersistentActor.java:29)<span class="error">&#91;188:org.opendaylight.controller.sal-clustering-commons:1.4.0.Boron&#93;</span><br/> at akka.persistence.UntypedPersistentActor.onReceive(PersistentActor.scala:170)<span class="error">&#91;182:com.typesafe.akka.persistence:2.4.7&#93;</span><br/> at org.opendaylight.controller.cluster.common.actor.MeteringBehavior.apply(MeteringBehavior.java:97)<span class="error">&#91;188:org.opendaylight.controller.sal-clustering-commons:1.4.0.Boron&#93;</span><br/> at akka.actor.ActorCell$$anonfun$become$1.applyOrElse(ActorCell.scala:544)<span class="error">&#91;176:com.typesafe.akka.actor:2.4.7&#93;</span><br/> at akka.actor.Actor$class.aroundReceive(Actor.scala:484)<span class="error">&#91;176:com.typesafe.akka.actor:2.4.7&#93;</span><br/> at akka.persistence.UntypedPersistentActor.akka$persistence$Eventsourced$$super$aroundReceive(PersistentActor.scala:168)<span class="error">&#91;182:com.typesafe.akka.persistence:2.4.7&#93;</span><br/> at akka.persistence.Eventsourced$$anon$1.stateReceive(Eventsourced.scala:633)<span class="error">&#91;182:com.typesafe.akka.persistence:2.4.7&#93;</span><br/> at akka.persistence.Eventsourced$class.aroundReceive(Eventsourced.scala:179)<span class="error">&#91;182:com.typesafe.akka.persistence:2.4.7&#93;</span><br/> at akka.persistence.UntypedPersistentActor.aroundReceive(PersistentActor.scala:168)<span class="error">&#91;182:com.typesafe.akka.persistence:2.4.7&#93;</span><br/> at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)<span class="error">&#91;176:com.typesafe.akka.actor:2.4.7&#93;</span><br/> at akka.actor.ActorCell.invoke(ActorCell.scala:495)<span class="error">&#91;176:com.typesafe.akka.actor:2.4.7&#93;</span><br/> at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)<span class="error">&#91;176:com.typesafe.akka.actor:2.4.7&#93;</span><br/> at akka.dispatch.Mailbox.run(Mailbox.scala:224)<span class="error">&#91;176:com.typesafe.akka.actor:2.4.7&#93;</span><br/> at akka.dispatch.Mailbox.exec(Mailbox.scala:234)<span class="error">&#91;176:com.typesafe.akka.actor:2.4.7&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)<span class="error">&#91;172:org.scala-lang.scala-library:2.11.8.v20160304-115712-1706a37eb8&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)<span class="error">&#91;172:org.scala-lang.scala-library:2.11.8.v20160304-115712-1706a37eb8&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)<span class="error">&#91;172:org.scala-lang.scala-library:2.11.8.v20160304-115712-1706a37eb8&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)<span class="error">&#91;172:org.scala-lang.scala-library:2.11.8.v20160304-115712-1706a37eb8&#93;</span></p> <p>karthikeyan,</p> <p> Few clarifications are needed here. When the service is started, what is the output of sudo ovs-vsctl show.</p> <p>a. Did Netvirt create the br-int after the restart and set-manager again?</p> <p>b. Also, Did you create instances and attempt the ping?, am wondering the flows related to tunnel are programmed when instances are created. Can you please provide more details so that we can check this immediately?</p> <p>(In reply to Venkatrangan Govindarajan from comment #4)<br/> &gt; karthikeyan,<br/> &gt; <br/> &gt; Few clarifications are needed here. When the service is started, what is<br/> &gt; the output of sudo ovs-vsctl show.<br/> &gt; <br/> &gt; a. Did Netvirt create the br-int after the restart and set-manager again?<br/> &gt; <br/> &gt; b. Also, Did you create instances and attempt the ping?, am wondering the<br/> &gt; flows related to tunnel are programmed when instances are created. Can you<br/> &gt; please provide more details so that we can check this immediately?</p> <p>When the service is started, there is no flows installed. and Yes, br-int is created after the restart. after set-manager, again there is no flows installed.</p> <p>We created instance's, and while checking IP is not assigned. but flows are installed only related to VM (table:20, 40, 90 and 110).</p> <p>This patch for <a href="https://jira.opendaylight.org/browse/NETVIRT-240" title="Pipeline flows are not consistently installed on OVS node with pre-existing integration bridge" class="issue-link" data-issue-key="NETVIRT-240"><del>NETVIRT-240</del></a> should also address this issue:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/48024" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/48024</a></p> <p>(In reply to Bertrand Low from comment #6)<br/> &gt; This patch for <a href="https://jira.opendaylight.org/browse/NETVIRT-240" title="Pipeline flows are not consistently installed on OVS node with pre-existing integration bridge" class="issue-link" data-issue-key="NETVIRT-240"><del>NETVIRT-240</del></a> should also address this issue:<br/> &gt; <a href="https://git.opendaylight.org/gerrit/#/c/48024" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/48024</a></p> <p>if ovs connected to odl in active mode, the stop of ovs will cause configured and optional data be delete in odl.</p> <p>Hi QianYu,</p> <p>the patch for <a href="https://jira.opendaylight.org/browse/NETVIRT-240" title="Pipeline flows are not consistently installed on OVS node with pre-existing integration bridge" class="issue-link" data-issue-key="NETVIRT-240"><del>NETVIRT-240</del></a> appears to resolve this bug now. Do you agree that we can close this bug as well now?</p> <p>thanks,<br/> Bertrand</p> <p>Bug has been fixed by patch <a href="https://git.opendaylight.org/gerrit/#/c/48024" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/48024</a></p> <p>Fix has been verified so bug can be closed.</p> <p>(In reply to Bertrand Low from comment #8)<br/> &gt; Hi QianYu,<br/> &gt; <br/> &gt; the patch for <a href="https://jira.opendaylight.org/browse/NETVIRT-240" title="Pipeline flows are not consistently installed on OVS node with pre-existing integration bridge" class="issue-link" data-issue-key="NETVIRT-240"><del>NETVIRT-240</del></a> appears to resolve this bug now. Do you agree that we<br/> &gt; can close this bug as well now?<br/> &gt; <br/> &gt; thanks,<br/> &gt; Bertrand</p> <p>yes, i agreed. please close this bug</p> <p>thanks</p> <p>Bug has been fixed by the below patch,<br/> <a href="https://git.opendaylight.org/gerrit/#/c/48024" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/48024</a></p> <p>Hence closing this bug.</p> Development External issue ID 6944 External issue URL Rank 0|i01qdb: