Device delete request returns response before the device removal is fully completed.

When user sends a DELETE request to /restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules/module/odl-sal-netconf-connector-cfg:sal-netconf-connector/$DEVICE_NAME (where $DEVICE_NAME is a name of a device mounted via netconf-connector), the response is sent before the device removal is fully completed. This can be observed by executing a GET request to /restconf/operational/network-topology:network-topology/topology/topology-netconf (the device $DEVICE_NAME will still be mentioned in the returned data).

This is most likely going to be a problem as most applications using an API like this assume the device is completely released once a "disconnect" request replies with the OK response. The behavior of netconf breaks this assumption which might cause corruption of the data on the device once the DELETE requestor tries to access the device in a way that is not netconf mount compatible.