This is almost exactly the same as NETCONF-446 but the data is different (although still XML) and there are no bundle refreshes, so this seems unrelated to ODLPARENT-110.

method: PUT
URL: 127.0.0.1:8181/restconf/config/openconfig-network-instance:network-instances/network-instance/global-bgp/openconfig-network-instance:protocols/protocol/openconfig-policy-types:BGP/example-bgp-rib/bgp/neighbors/neighbor/10.29.12.214
data: <neighbor xmlns="urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions">
<neighbor-address>10.29.12.214</neighbor-address>
<route-reflector>
<config>
<route-reflector-client>false</route-reflector-client>
</config>
</route-reflector>
<timers>
<config>
<hold-time>180</hold-time>
</config>
</timers>
<transport>
<config>
<remote-port>17900</remote-port>
<passive-mode>true</passive-mode>
</config>
</transport>
<config>
<peer-type>INTERNAL</peer-type>
<auth-password>topsecret</auth-password>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:IPV4-UNICAST</afi-safi-name>
</afi-safi>
</afi-safis>
</neighbor>

The long response [0] starts with:
<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"><error><error-type>application</error-type><error-tag>operation-failed</error-tag><error-message>canCommit encountered an unexpected failure</error-message><error-info>org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaValidationFailedException: Child /(http://openconfig.net/yang/network-instance?revision=2015-10-18)network-instances/network-instance/network-instance[

]/protocols/protocol/protocol[

]/AugmentationIdentifier

/(urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions?revision=2016-06-14)bgp/neighbors/neighbor/neighbor[

]/neighbor[

] is not present in schema tree.

Similarly to NETCONF-446 the last segment of path (neighbor[] in this case) appears twice, so that might be the bug.

[0] https://logs.opendaylight.org/releng/jenkins092/bgpcep-csit-1node-userfeatures-only-nitrogen/106/log.html.gz#s1-s3-t1-k1-k2-k1-k4-k7-k1