OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [NETCONF-281] Forgotten config DS changes when no clustered topology owner https://jira.opendaylight.org/browse/NETCONF-281 netconf <p>When there is no Owner for topology-manager entity, changes in config topology-netconf are not processed. When new owner appears, it does not examine state of topology-netconf. That means some user-configured connections are never opened, and some user-deconfigured connections are never torn down.</p> <p>As lack of owner is not visible in Restconf output, current users can never be sure whether their changes will ever be applied.</p> <p>Similar behavior was present in Openflowplugin project for Forwarding Rules Manager (FRM). They created FRS, S meaning Synchronize.</p> <p>For Netconf, I recommend to add synchronization ability directly to odl-netconf-clustered_topology.<br/> And possibly odl-netconf-topology as well, in order to re-establish previously configured connections after reboot in single node scenario.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-281 Forgotten config DS changes when no clustered topology owner Bug Confirmed Unresolved Unassigned Vratko Polak Wed, 21 Sep 2016 13:56:51 +0000 Tue, 13 Aug 2019 07:38:39 +0000 netconf 0 2 <p>This should be fixed in new refactored clustered netconf topology implementation.</p> <p>Please see <a href="https://jira.opendaylight.org/browse/NETCONF-277" title="Use singleton service in clustered netconf topology" class="issue-link" data-issue-key="NETCONF-277"><del>NETCONF-277</del></a></p> <p>INVALID means the reported issue was a user error and not a real Bug.</p> <p>If this is will be fixed together with another Bug, this should be kept CONFIRMED or perhaps marked as DUPLICATE.</p> <p>Sorry,</p> <p>We will have to try to replicate this on new clustered topology to see if the bug is still present..</p> Blocks NETCONF-277 Development External References netconf_cluster_stress_txt_topology_owner_ha_check_for_connector_leak External issue ID 6774 External issue URL Issue Type Rank 0|i01xkn: