-
Bug
-
Resolution: Done
-
Medium
-
7.0.0, 7.0.1
This issue is present on current main branch targeting NETCONF 7.
Invoke PUT:
http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf
With content:
{ "topology": { "topology-id": "topology-netconf", "node": [ { "node-id": "netopeer2A", "netconf-node-topology:key-based": { "username": "netconf", "key-id": "device-key-A" }, "netconf-node-topology:schemaless": false, "netconf-node-topology:port": 830, "netconf-node-topology:tcp-only": false, "netconf-node-topology:keepalive-delay": 0, "netconf-node-topology:host": "127.0.0.1", "netconf-node-topology:max-connection-attempts": 5 }, { "node-id": "netopeer2B", "netconf-node-topology:key-based": { "username": "netconf", "key-id": "device-key-B" }, "netconf-node-topology:schemaless": false, "netconf-node-topology:port": 830, "netconf-node-topology:tcp-only": false, "netconf-node-topology:keepalive-delay": 0, "netconf-node-topology:host": "127.0.0.1", "netconf-node-topology:max-connection-attempts": 5 } ] } }
The result is GET:
http://localhost:8181/rests/data/network-topology:network-topology/topology=topology-netconf?fields=node/node-id;node/netconf-node-topology:connection-status&content=all
With body:
{ "network-topology:topology": [ { "node": [ { "node-id": "netopeer2A", "netconf-node-topology:connection-status": "connecting" }, { "node-id": "netopeer2B" } ] } ] }
The netopeer2B device is missing connection-status. In fact, the whole operational state for this device is missing try to use (content=nonconfig).
We expect operational state to be present for all devices.