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/NETCONF-130 netconf <p>It seems like odl-netconf-connector-ssh feature in Beryllium (and Boron) is not ready for cluster deployment, as it can lead to "server unhealthy" error state.</p> <p>See <span class="error">&#91;0&#93;</span> for recent example, where the reason is:</p> <p>2016-01-22 10:54:10,205 | WARN | lt-dispatcher-18 | SimpleShardDataTreeCohort | 154 - org.opendaylight.controller.sal-distributed-datastore - 1.4.0.SNAPSHOT | Store Tx member-3-chn-2-txn-1: Conflicting modification for path /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=controller-config} <p>].<br/> 2016-01-22 10:54:10,206 | ERROR | lt-dispatcher-44 | LocalThreePhaseCommitCohort | 154 - org.opendaylight.controller.sal-distributed-datastore - 1.4.0.SNAPSHOT | Failed to prepare transaction member-3-chn-2-txn-1 on backend<br/> OptimisticLockFailedException</p> {message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]]} <p>Of course, there is odl-netconf-clustered-topology feature to be used with cluster, but that does not initiate the self-connection (controller-config device) that is needed for users who want to re-configure ODL in runtime using restconf.</p> <p>Is there a way to use netconf-connector functionality in 3-node cluster?</p> <p><span class="error">&#91;0&#93;</span> <a href="https://jenkins.opendaylight.org/releng/job/controller-csit-verify-3node-clustering/54/consoleFull" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/controller-csit-verify-3node-clustering/54/consoleFull</a></p> <p>Operating System: All<br/> Platform: All</p> NETCONF-130

Netconf connector not safe in 3-node cluster

Bug Resolved Won't Do Unassigned Vratko Polak Mon, 25 Jan 2016 12:39:08 +0000 Fri, 15 Mar 2019 22:22:19 +0000 Mon, 1 Feb 2016 14:31:52 +0000 netconf 0 2 <p>This is a limitation of cfg subsystem and CDS.<br/> Since the controller-config loopback connection corresponds to a different<br/> entity on each node(separate netconf server per node) the operational data of<br/> the connector's should not be clustered since as you can see the connector's<br/> are overwriting each other's data.</p> <p>Since the controller-config connection is just a preconfigured netconf<br/> connector that connects to the cfg subsystem netconf server on localhost<br/> a possible workaround is to manually start a clustered connector for each<br/> cfg-subsystem server in the cluster. You would then have to differentiate these<br/> with different node id's(ex. controller-config-node1). You will also for example<br/> be able to post configuration meant for cfg subsystem on other nodes to a single node.</p> <p>So the title of this Bug is the expected behavior.<br/> Setting to WONTFIX; there is no official requirement to make netconf-connector cluster-proof, as there is odl-netconf-clustered-topology feature.</p> <p>Wikipage for testers is created <span class="error">&#91;0&#93;</span>. Is there an authoritative wikipage from netconf (or controller) project?</p> <p><span class="error">&#91;0&#93;</span> <a href="https://wiki.opendaylight.org/view/Integration/Test/Cluster_Incompatible_Features#odl-netconf-connector" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Integration/Test/Cluster_Incompatible_Features#odl-netconf-connector</a></p> Development External issue ID 5079 External issue URL Issue Type Rank 0|i01wn3: