NSO LSA tsdn 5.0 M7 -commands for "RPL association" removal are not created and not pushed to the device: The issue is only on NSO LSA - in NSO standalone (with the same M7) the commands for the update are pushed correctly to the device.CFS - 10.56.116.131, RFS 1 - 10.56.116.133, RFS 2 - 10.56.116.134 (credentials for all: nso/Public1234!)Steps to reproduce:1. I created l3vpn service over SR-ODN named "v6-l3vpn_114_117-420_odn" &#8211; see attached payload with ODN templates, RPLs, service. 2. After service configs were pushed to the devices (service has two endpoints on 192.168.255.114 and 192.168.255.117 devices) and ODN templates become instantiated and UP - I did (via NSO UI, same issue via CW UI) removal of export route-policy association from 192.168.255.114 endpoint &#8211; see attached snapshot with changesNow I am seeing the following issues:a) I checked the native config section - no configs are being generatedb) After pressing Commit button - NSO reported success, but configs for "export route policy" removal (or any other commands) were NOT pushed to the device.I collected logs using get_technical_support_data.sh from CFS and RFS nodes and copied them to the folder in box: 
 FiledHi Leonid,We were not able to reproduce the issue in our setup and can see that the config is being removed properly when removing the export route-policy association.Please help us with your system details to check this issue further.Thanks,NikhilWhich "system details" are needed?In the same NSO that I already mentioned (10.56.116.131) and the same service - I tried again and there no device commands shown in "native config":the only thing that is shown is:rfs-1<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"   message-id="1"> <edit-config xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">  <target>   <running/>  </target>  <test-option>test-then-set</test-option>  <error-option>rollback-on-error</error-option>  <with-inactive xmlns="http://tail-f.com/ns/netconf/inactive/1.0"/>  <config>   <flat-L3vpn xmlns="http://cisco.com/ns/nso/fp/examples/cisco-tsdn-flat-L3vpn-internal">    <name>L3NM-v6-l3vpn_114_117-420_odn-internal</name>    <endpoint-name>192.168.255.114_114</endpoint-name>    <endpoint>     <endpoint-name>192.168.255.114_114</endpoint-name>     <sr-te>      <odn>       <route-policy xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"              nc:operation="delete">        <route-policy-name>l3-rpl-114_305</route-policy-name>       </route-policy>      </odn>     </sr-te>     <vrf>      <address-family>       <address-family>ipv6</address-family>       <export-route-policy-name xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"                    nc:operation="delete"/>      </address-family>     </vrf>    </endpoint>   </flat-L3vpn>  </config> </edit-config></rpc>If commit is pressed the "removal" commands are not being pushed to the device also.Hi Leonid,As discussed during our meetings, there was some issue in the setup, the service was not owning the config and hence the config on the device was not getting removed. We did a cleanup of the service, cleared the config on the device and then created the service again which was working fine as expected.The configs are now getting removed properly from the device while removing the association of route policy.Hence closing the issue.Thanks,NikhilCleaned up the service and config and the functionality was working fine after that.