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-280 netconf <p>when modifying the configuration of a mounted device in response to a RESTCONF PUT or POST request ODL locks the candidate configuration, however it doesn't lock the running configuration.</p> <p>this risks a race condition where the running configuration is edited by another user (e.g. from the CLI) before ODL commits the configuration changes.</p> <p>is it possible to apply a lock to the running configuration as well as the candidate configuration?</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-280

need to lock running as well as candidate config in mounted device

Bug Resolved Won't Do Jakub Morvay Giles Heron Mon, 19 Sep 2016 18:52:19 +0000 Fri, 15 Mar 2019 22:22:30 +0000 Fri, 14 Oct 2016 08:47:51 +0000 netconf 0 1 <p>Hi Giles,</p> <p>I have quickly checked the implementation and ODL should lock both candidate and running configurations.</p> <p>Does your device advertise :writable-running capability?</p> <p>no - the device doesn't advertise :writeable-running.</p> <p>but we'd still like running to be locked to prevent other users changing it.</p> <p>But is there a way how you can change it then?</p> <p>Anyway I think you can issue a lock through RESTCONF, then edit configuration and finally unlock the device.</p> <p>(In reply to Jakub Morvay from comment #3)<br/> &gt; But is there a way how you can change it then?</p> <p>you can change the config from the CLI if running-config isn't locked.</p> <p>&gt; Anyway I think you can issue a lock through RESTCONF, then edit<br/> &gt; configuration and finally unlock the device.</p> <p>The device doesn't expose "ietf-netconf" so there's no way to use RESTCONF to issue a lock command. Even if it did I'd say that's a bit of a kludge...</p> <p>Ok then, we can lock also running configuration for devices that advertise just :candidate capability and no :writable-running capability</p> <p>thanks!</p> <p>ah - looks like we don't need this one after all. The box in question implicitly locks running config if you lock candidate...</p> <p>I'm closing this bug as locking candidate configuration implicitly could break some devices out there.</p> <p>After <a href="https://jira.opendaylight.org/browse/NETCONF-250" title="Allow over-ride of non-module capabilities" class="issue-link" data-issue-key="NETCONF-250"><del>NETCONF-250</del></a> will be resolved, one can override also non module capabilities advertised by device and can add :writable-running capability, so the ODL would lock also running configuration.</p> Development External issue ID 6750 External issue URL Rank 0|i01xkf: