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/CONTROLLER-1452 controller <p>I found that pre-provision is not happening when the switch gets connected with follower node. But at the same time, when the switch is connected with leader node, switch gets all the flows.</p> <p>I am seeing this issue in 3 # node cluster and build version is distribution-karaf-0.3.3-Lithium-SR3.zip</p> <p>I tested this in following cases;</p> <p>case 1: configure flows in leader node <br/> -------------------------------------------</p> <p> a. connect the switch in leader node &#8211; pre-provision is working<br/> b. Connect the switch in follower node - pre-provision is not working </p> <p>case 2: configure flows in either of follower node<br/> ---------------------------------------------------</p> <p> a. Connect the switch in leader node &#8211; pre-provision is working<br/> b. connect the switch in either of the follower node &#8211; pre-provision is not working.</p> <p>here with I am enclosing <br/> opendaylight-inventory-nodes-operational-follower-node (open it in notepad / winword)<br/> opendaylight-inventory-nodes-config-follower2 (can open it in notepad /winword)<br/> follower2 --(pcap file, open it in wireshark)<br/> karaf.log (open it in notepad)</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1452

3 # cluster : Pre-provision is not happening when the switch is connected with follower node

Bug Resolved Duplicate Unassigned Anpukarasi Muthukumaran Tue, 24 Nov 2015 12:52:41 +0000 Thu, 19 Oct 2017 21:26:33 +0000 Wed, 27 Jan 2016 08:27:32 +0000 Lithium clustering 0 6 <p>Attachment karaf.log has been added with description: karaf.log</p> <p>Is this just a dup of 4665?</p> <p>Is trhis reproducible in Be?</p> <p>I think we fixed this:<br/> 2015-11-23 00:50:23,754 | WARN | ult-dispatcher-3 | ShardManager | 207 -<br/> org.opendaylight.controller.sal-distributed-datastore - 1.2.3.Lithium-SR3 | Supervisor<br/> Strategy caught unexpected exception - resuming<br/> org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaValidationFailedExcepti<br/> n: Child [] is not present in schema tree.<br/> at<br/> org.opendaylight.yangtools.yang.data.impl.schema.tree.InMemoryDataTreeModificationC<br/> rsor.resolveChildModification(InMemoryDataTreeModificationCursor.java:55<br/> <span class="error">&#91;90:org.opendaylight.yangtools.yang-data-impl:0.7.3.Lithium-SR3&#93;</span><br/> at<br/> org.opendaylight.yangtools.yang.data.impl.schema.tree.InMemoryDataTreeModificationC<br/> rsor.write(InMemoryDataTreeModificationCursor.java:112<br/> <span class="error">&#91;90:org.opendaylight.yangtools.yang-data-impl:0.7.3.Lithium-SR3&#93;</span><br/> at<br/> org.opendaylight.yangtools.yang.data.api.schema.tree.DataTreeCandidates.applyToPar<br/> ntCursor(DataTreeCandidates.java:99)[80:org.opendaylight.yangtools.yang-data<br/> api:0.7.3.Lithium-SR3]<br/> at<br/> org.opendaylight.yangtools.yang.data.api.schema.tree.DataTreeCandidates.applyToRoo<br/> Cursor(DataTreeCandidates.java:116)[80:org.opendaylight.yangtools.yang-data<br/> api:0.7.3.Lithium-SR3]<br/> atorg.opendaylight.yangtools.yang.data.api.schema.tree.DataTreeCandidates.applyToCur<br/> or(DataTreeCandidates.java:48)[80:org.opendaylight.yangtools.yang-data<br/> api:0.7.3.Lithium-SR3]<br/> at<br/> org.opendaylight.yangtools.yang.data.api.schema.tree.DataTreeCandidates.applyToMod<br/> fication(DataTreeCandidates.java:36)[80:org.opendaylight.yangtools.yang-data<br/> api:0.7.3.Lithium-SR3]<br/> at<br/> org.opendaylight.controller.cluster.datastore.ShardDataTree.applyForeignCandidate(Sha<br/> dDataTree.java:178)[207:org.opendaylight.controller.sal-distributed<br/> datastore:1.2.3.Lithium-SR3]<br/> at</p> <p>Robert says that there are failures to replicate data because of empty data items in the logs on BUG4665, but he thinks that's fixed in Berylilum.</p> <p>He also says that he sees empty child issues that are fixed in Beryllium, also OpenFlow plugin connection and disconnection.</p> <p>See if this can be reproduced in Beryllium. Also, confirm that the relevant things have been fixed on stable/lithium.</p> <p>I still see it in Beryllium release, i am investigating it and will provide more details on how to recreate it.</p> <p>Although the exception i am seeing in my environment says </p> <p>Supervisor Strategy caught unexpected exception - resuming</p> <p>but it's happening because of NPE, while doing cluster data replication. I will open another bug for that.</p> <p>The current theory is that this is caused by Bug-5019. Anil, can you confirm?</p> <p>The main issue is happening probably because of some issue in RPC routing. If switch connects to follower node then RPC for the switch will be registered on the follower. In this case RPC needs to be routed to follower from leader, and i think there is some issue there. I am not entirely sure if "Supervisor<br/> Strategy caught unexpected exception" - <a href="https://jira.opendaylight.org/browse/CONTROLLER-1475" title="Supervisor Strategy caught unexpected exception because of NPE in NormalizedNodeInputStreamReader" class="issue-link" data-issue-key="CONTROLLER-1475"><del>CONTROLLER-1475</del></a> can impact this behavior. If it can, i can test it in my environment, but i think all the related patch for 5019 are not merged yet? I will try to build controller, yangtools locally and test it, if we want to verify it before merging the relevant patches.</p> Duplicate CONTROLLER-1475 CONTROLLER-1453 Development External issue ID 4664 External issue URL Priority Rank 0|i02qnr: