https://jira.opendaylight.org/browse/NETCONF-657 (useful resources and links in the comments)

Workflow...

1. Create YANG models suitable for reproduction and confirm with reporter (DONE)
2. Confirm buggy behavior (IN-PROGRESS)
3. Review NETCONF code around defect
4. Propose change/design
5. Implement unit test showing defect
6. Implement code change
7. Get QA sign off on feature coverage
8. Get 3rd party acceptance of implementation (see original reporter, Frank Sandoval @ Lumina)
9. PR and review process

Resources...
https://tools.ietf.org/html/rfc8040#section-1.1.6 (RESTCONF)
https://tools.ietf.org/html/draft-ietf-netconf-yang-patch-14 (Yang Patch)
https://docs.opendaylight.org/en/latest/developer-guide/yang-tools.html (YangTools)
https://tools.ietf.org/html/rfc7950 (Yang)

karaf> feature:install odl-restconf odl-netconf-topology odl-restconf-nb-rfc8040 odl-netconf-connector-all

Ran testtool loaded with directory of attached Yang models...

echo "Starting testtool (port=17830,cred=admin/admin) using extra schemas..."
java -jar ./netconf/tools/netconf-testtool/target/netconf-testtool-*-SNAPSHOT-executable.jar  --device-count 1  --schemas-dir ./extra_schemas/netconf-658b --md-sal true

Use the attached Postman collection to mount testtool as device, create content, apply query

So I got the back haul model 3 Yang files loaded into testtool (acting as a device).

I made minor modifications by commenting out some of the model so my payloads were simpler.

I created an instance in the device and the read gave this, which looks fine to me:

<control-construct xmlns="urn:onf:yang:core-model-1-4">

<logical-termination-point>

<uuid>xyz</uuid>

<layer-protocol>

<local-id>foobar</local-id>

<ethernet-container-pac xmlns="urn:onf:yang:ethernet-container-2-0">

<ethernet-container-current-problems>

<current-problem-list>

<sequence-number>3</sequence-number>

<problem-severity>SEVERITY_TYPE_MINOR</problem-severity>

<timestamp>2020-03-06T11:00:02Z</timestamp>

</current-problem-list>

<current-problem-list>

<sequence-number>2</sequence-number>

<timestamp>2020-03-06T11:00:01Z</timestamp>

<problem-name>bar</problem-name>

</current-problem-list>

<current-problem-list>

<sequence-number>1</sequence-number>

<problem-severity>SEVERITY_TYPE_CRITICAL</problem-severity>

<timestamp>2020-03-06T11:00:00Z</timestamp>

<problem-name>foo</problem-name>

</current-problem-list>

</ethernet-container-current-problems>

</ethernet-container-pac>

</layer-protocol>

</logical-termination-point>

</control-construct>

I ran the original query URL (ignore the missing content type) from the JIRA issue, shown below:

http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool/yang-ext:mount/core-model-1-4:control-construct?fields=logical-termination-point(local-id;layer-protocol(administrative-state);ethernet-container-2-0:ethernet-container-pac(ethernet-container-current-problems))

It resulted in the following error:

<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">

<error>

<error-message>Child ethernet-container-pac node missing in logical-termination-point</error-message>

<error-tag>invalid-value</error-tag>

<error-type>protocol</error-type>

</error>

</errors>

I think that URL is not compatible with the Yang model. I changed the query URL to be:

http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=testtool/yang-ext:mount/core-model-1-4:control-construct?fields=logical-termination-point(local-id;layer-protocol(administrative-state;ethernet-container-2-0:ethernet-container-pac(ethernet-container-current-problems)))

So this resulted in a successful query, yielding:

<control-construct xmlns="urn:onf:yang:core-model-1-4">

<logical-termination-point>

<layer-protocol>

<ethernet-container-pac xmlns="urn:onf:yang:ethernet-container-2-0">

<ethernet-container-current-problems>

<current-problem-list>

<sequence-number>3</sequence-number>

<problem-severity>SEVERITY_TYPE_MINOR</problem-severity>

<timestamp>2020-03-06T11:00:02Z</timestamp>

</current-problem-list>

<current-problem-list>

<sequence-number>2</sequence-number>

<timestamp>2020-03-06T11:00:01Z</timestamp>

<problem-name>bar</problem-name>

</current-problem-list>

<current-problem-list>

<sequence-number>1</sequence-number>

<problem-severity>SEVERITY_TYPE_CRITICAL</problem-severity>

<timestamp>2020-03-06T11:00:00Z</timestamp>

<problem-name>foo</problem-name>

</current-problem-list>

</ethernet-container-current-problems>

</ethernet-container-pac>

</layer-protocol>

</logical-termination-point>

</control-construct>

So the original URL shows an error that is really more of a “typo” in the query.

Not a bug. User error.