Uploaded image for project: 'netconf'
  1. netconf
  2. NETCONF-240

Data augmentation doesn't work with notifications

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Duplicate
    • None
    • None
    • restconf-nb
    • None
    • Operating System: All
      Platform: All

    • 6301

    Description

      Observed an interesting situation with notifications.

      when I have data that got augmented (by some other yang file),and use the base data for notification, it doesn't work.

      I think as per RFC (https://tools.ietf.org/pdf/rfc6020.pdf) it is supposed to work.

      I keep getting the following error(and similar ones) during Delivery.

      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
      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.
      at org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException.create(IncorrectNestingException.java:28)
      at org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext.childNonNull(DataContainerCodecContext.java:180)[66:org.opendaylight.mdsal.binding-dom-codec:0.8.1.Beryllium-SR1]
      at o

      I will update the bug with more details

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              jakubtoth-0 Jakub Toth
              hari@harinath.in Harinath Mallepally
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: