FYI, a mount to config store like below does work. this is just failing with the create-device RPC:

{
    "network-topology:node": {
        "node-id": "{{node}}",
        "netconf-node-topology:host": "{{testtool-ip}}",
        "schema-cache-directory": "{{testtool-ip}}",
        "netconf-node-topology:port": 830,
        "netconf-node-topology:tcp-only": false,
        "netconf-node-topology:username": "jamo",
        "netconf-node-topology:password": "jamo123",
        "netconf-node-topology:actor-response-wait-time": 60,
        "netconf-node-topology:keepalive-delay": 60,
        "netconf-node-optional:ignore-missing-schema-sources": {
            "reconnect-time": 2000,
            "allowed": true
        }
    }
}

jluhrsen
Please give URL also for this config store which is working.

nikhil.soni.lumina,

this is the working case:

PUT to:

http://{{controller-ip}}:8181/restconf/config/network-topology:network-topology/topology/topology-netconf

with body:

{
    "network-topology:node": {
        "node-id": "{{node}}2",
        "netconf-node-topology:host": "{{testtool-ip}}",
        "netconf-node-topology:port": 830,
        "netconf-node-topology:tcp-only": false,
        "netconf-node-topology:username": "jamo",
        "netconf-node-topology:password": "jamo123",
        "netconf-node-topology:actor-response-wait-time": 600,
        "netconf-node-topology:keepalive-delay": 600,
        "netconf-node-optional:ignore-missing-schema-sources": {
            "reconnect-time": 5000,
            "allowed": true
        }
    }
}

vs the failing case described above using the create-device RPC

jluhrsen

I have investigated the issue and have found below points -

1. There is a Yang file named netconf-node-optional which has augment for Node "/nt:network-topology/nt:topology/nt:node". This augment enables extra fields in network-topology->topolpgy->node but not for the rpc.

2. if we call "restconf/operations/netconf-node-topology:create-device" with above augment fields then in RestConf filter it throws "ignore-missing-schema-sources was not found" which is valid.

To justify point 2, at local I changed netconf-node-optional augment with augment "/nt:create-device/nt:input/"
then I executed the rpc URL with same payload and it worked in unit test.

With above points, it does not look that it is an issue.

Please suggest if you have any other point of view.

nikhil.soni.lumina, it sounds like you have the fix right? You can include the unit test with the augment change.

But, I'm not sure we are on the same page because you said "it does not look that it is an issue."

let me know what you think.

jluhrsen
Rewording my reply without example -

There is a Yang file named netconf-node-optional which has augment for Node "/nt:network-topology/nt:topology/nt:node".

So according to this file only "/restconf/config/network-topology:network-topology/topology/topology-netconf" Rest call will work with "ignore-missing-schema-sources" payload field.

So according to "netconf-node-optional" Yang file below scenarios are valid -

1. Rest call /restconf/operations/netconf-node-topology:create-device should throw exception "Schema node with name ignore-missing-schema-sources was not found under" if we pass ignore-missing-schema-sources field in payload - it is happening in current implementation

2.Rest call /restconf/config/network-topology:network-topology/topology/topology-netconf should accept "ignore-missing-schema-sources" field - it is happening in current implementation

nikhil.soni.lumina as discussed, please go ahead and raise a gerrit with the augmentation change.