Medium This is shown in this test suite:
https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-oxygen/
I see when this RPC is invoked:
restconf/operations/netconf-node-topology:add-netconf-node <input xmlns="urn:opendaylight:netconf-node-topology"> <node-id>netconf-test-device</node-id> <encrypt>true</encrypt> <host>10.30.170.85</host> <port>17830</port> <username>admin</username> <password>topsecret</password> <tcp-only>false</tcp-only> <keepalive-delay>0</keepalive-delay> </input>
Controller responds with:
<errors> xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>protocol</error-type> <error-tag>invalid-value</error-tag> <error-message>URI has bad format. Possible reasons: 1. "netconf-node-topology:add-netconf-node" was not found in parent data node. 2. "netconf-node-topology:add-netconf-node" is behind mount point. Then it should be in format "/yang-ext:mount/netconf-node-topology:add-netconf-node".</error-message> </error> </errors>
Adding device via topology config works fine and the above RPC works in Nitrogen so unless there is an expected and documented API change in Oxygen, this is a BLOCKER for Oxygen.