https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-240 netconf <p>Observed an interesting situation with notifications.</p> <p>when I have data that got augmented (by some other yang file),and use the base data for notification, it doesn't work.</p> <p>I think as per RFC (<a href="https://tools.ietf.org/pdf/rfc6020.pdf" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/pdf/rfc6020.pdf</a>) it is supposed to work.</p> <p>I keep getting the following error(and similar ones) during Delivery.</p> <p>2016-07-27 13:57:06,788 | ERROR | pool-28-thread-1 | DOMNotificationRouterEvent | 115 - org.opendaylight.controller.sal-broker-impl - 1.3.1.Beryllium-SR1 | Delivery of notification org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@5baeac9 caused an error in listener org.opendaylight.netconf.sal.streams.listeners.NotificationListenerAdapter@c087ae7<br/> org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException: Child interface org.opendaylight.yang.gen.v1.urn.infinera.params.xml.ns.yang.infn.otn.service.rev160425.TunnelUpdateTimeAugment is not valid child.<br/> at org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException.create(IncorrectNestingException.java:28)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext.childNonNull(DataContainerCodecContext.java:180)<span class="error">&#91;66:org.opendaylight.mdsal.binding-dom-codec:0.8.1.Beryllium-SR1&#93;</span><br/> at o</p> <p>I will update the bug with more details</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-240

Data augmentation doesn't work with notifications

Bug Resolved Duplicate Jakub Toth Harinath Mallepally Thu, 28 Jul 2016 22:30:53 +0000 Fri, 15 Mar 2019 22:22:27 +0000 Mon, 28 Nov 2016 12:37:36 +0000 restconf-nb 0 1 <p>Additional inputs</p> <p>The we I could make it work is in all yang files that I used for data augmentation, I duplicated it to augment notification data too.</p> <p>example:</p> <p> augment "/te:te/te:tunnels/te:tunnel/te:config/te:endpoint" </p> { description "Augment with additional parameters required for OTN service."; ext:augment-identifier otn-tunnel-endpoint-config-augment; uses otn-tunnel-endpoint; } <p> augment "/te:tunnel-lifecycle-event/te:config/te:endpoint" </p> { description "Augment the tunnel lifecycle event with additional parameters required for OTN service."; ext:augment-identifier tunnel-lifecycle-event-otn-tunnel-endpoint-config-augment; uses otn-tunnel-endpoint; } <p>Then I could make it work, but this is error prone right? I think we should have the augmented data be processed through notification without any explicit augmentation again, as this will result in duplicate code (mostly) and if missed, it will cause notifications delivery to fail.</p> <p>1. based on discussion with Jakub Toth, moving this bug to Restconf.<br/> He will come back with tests if this stays as restconf bug or we should<br/> move it to mdsal or yangtools (based on his results).<br/> 2. since latest beryllium SR4 code freeze happened yesterday,<br/> this should be fixed for Boron onwards.</p> Blocks NETCONF-245 Duplicate NETCONF-245 Development External issue ID 6301 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01xbj: