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-483 netconf <p>Netconf notifications from devices will sent with a parameter called event-time<br/> This is according to the RFC <a href="https://tools.ietf.org/html/rfc5277#section-2.2.1" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc5277#section-2.2.1</a> . </p> <p>When these notification are about to delivered to the registered listeners, an instance of generated POJO (from notification event model ) will be used to deliver the notification. Only modelled data is forwarded. Event time will be ignored.</p> <p>Due to this end user will not able to get when this event is generated. So Is there any way end user will be able to get this data as part of notification ?</p> NETCONF-483

Netconf Notification event-Time will not reach the end user

Bug High Resolved Cannot Reproduce Yaroslav Lastivka Karthik Holla pt Wed, 8 Nov 2017 12:36:47 +0000 Thu, 23 Feb 2023 12:52:27 +0000 Thu, 23 Feb 2023 12:49:39 +0000 netconf 0 5 <p>Since the bug is unassigned I'm currently assigning it to you.</p> <p>Please assign to the relevant person. </p> <p>As long as NETCONF performs encoding to an object which implements org.opendaylight.mdsal.dom.api.DOMEvent, this should actually work – users can either access it via DOMEvent or its Binding counterpart (org.opendaylight.yangtools.yang.binding.EventInstantAware) – i.e. upon reception of the DTO perform an instanceof check and cast it.</p> <p>This time will not be part of DTOs directly, as they are transport-level property – see RFC6241 figure 1,  POJOs are layer 4, event-time is at layer 2 (as part of &lt;notification/&gt;)</p> <p>We need to verify this with RFC8040. According to bierman-02 based steps to reproduce issue is no more present.</p> <p>I have tried to reproduce these steps and found out that with SSE the issue is not present.</p> <p>My logs:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> odl@odl-Latitude-5521:~$ curl -v -X GET  http:<span class="code-comment">//localhost:8181/rests/notif/data-change-event-subscription/network-topology:network-topology/datastore=CONFIGURATION/scope=SUBTREE  -H <span class="code-quote">"Content-Type: text/event-stream"</span> -H <span class="code-quote">"Authorization: Basic YWRtaW46YWRtaW4="</span> </span>Note: Unnecessary use of -X or --request, GET is already inferred.   Trying 127.0.0.1:8181... Connected to localhost (127.0.0.1) port 8181 (#0) &gt; GET /rests/notif/data-change-event-subscription/network-topology:network-topology/datastore=CONFIGURATION/scope=SUBTREE HTTP/1.1 &gt; Host: localhost:8181 &gt; User-Agent: curl/7.81.0 &gt; Accept: / &gt; Content-Type: text/event-stream &gt; Authorization: Basic YWRtaW46YWRtaW4= &gt;  Mark bundle as not supporting multiuse &lt; HTTP/1.1 200 OK &lt; Set-Cookie: JSESSIONID=node012x3457ld74yg1mvgjkzj18fst0.node0; Path=/rests; HttpOnly &lt; Expires: Thu, 01 Jan 1970 00:00:00 GMT &lt; Set-Cookie: rememberMe=deleteMe; Path=/rests; Max-Age=0; Expires=Tue, 07-Feb-2023 17:22:02 GMT; SameSite=lax &lt; Content-Type: text/event-stream &lt; Transfer-Encoding: chunked &lt;  : ping : ping : ping data: &lt;notification xmlns=<span class="code-quote">"urn:ietf:params:xml:ns:netconf:notification:1.0"</span>&gt;&lt;eventTime&gt;2023-02-08T19:22:33.99851211+02:00&lt;/eventTime&gt;&lt;data-changed-notification xmlns=<span class="code-quote">"urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote"</span>&gt;&lt;data-change-event&gt;&lt;path&gt;/urn-TBD-params-xml-ns-yang-network-topology:network-topology&lt;/path&gt;&lt;data&gt;&lt;network-topology xmlns=<span class="code-quote">"urn:TBD:params:xml:ns:yang:network-topology"</span>&gt;&lt;topology&gt;&lt;topology-id&gt;topology-netconf&lt;/topology-id&gt;&lt;node&gt;&lt;node-id&gt;17830-sim-device&lt;/node-id&gt;&lt;port xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;17830&lt;/port&gt;&lt;schemaless xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;<span class="code-keyword">false</span>&lt;/schemaless&gt;&lt;tcp-only xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;<span class="code-keyword">false</span>&lt;/tcp-only&gt;&lt;keepalive-delay xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;0&lt;/keepalive-delay&gt;&lt;username xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;admin&lt;/username&gt;&lt;password xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;admin&lt;/password&gt;&lt;host xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;127.0.0.1&lt;/host&gt;&lt;/node&gt;&lt;/topology&gt;&lt;/network-topology&gt;&lt;/data&gt;&lt;operation&gt;created&lt;/operation&gt;&lt;/data-change-event&gt;&lt;/data-changed-notification&gt;&lt;/notification&gt;   </pre> </div></div> <p>Reproducing steps using the WebSocket mechanism shows that the issue is not present.<br/> Logs:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> $ wscat --header <span class="code-quote">"Authorization: Basic YWRtaW46YWRtaW4="</span> -c ws:<span class="code-comment">//localhost:8181/rests/data-change-event-subscription/network-topology:network-topology/datastore=CONFIGURATION/scope=SUBTREE Connected (press CTRL+C to quit) &lt; &lt;notification xmlns=<span class="code-quote">"urn:ietf:params:xml:ns:netconf:notification:1.0"</span>&gt;&lt;eventTime&gt;2023-02-23T11:48:41.987760371+02:00&lt;/eventTime&gt;&lt;data-changed-notification xmlns=<span class="code-quote">"urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote"</span>&gt;&lt;data-change-event&gt;&lt;path&gt;/urn-TBD-params-xml-ns-yang-network-topology:network-topology&lt;/path&gt;&lt;data&gt;&lt;network-topology xmlns=<span class="code-quote">"urn:TBD:params:xml:ns:yang:network-topology"</span>&gt;&lt;topology&gt;&lt;topology-id&gt;topology-netconf&lt;/topology-id&gt;&lt;node&gt;&lt;node-id&gt;17830-sim-device&lt;/node-id&gt;&lt;port xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;17830&lt;/port&gt;&lt;schemaless xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;<span class="code-keyword">false</span>&lt;/schemaless&gt;&lt;tcp-only xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;<span class="code-keyword">false</span>&lt;/tcp-only&gt;&lt;keepalive-delay xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;0&lt;/keepalive-delay&gt;&lt;username xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;admin&lt;/username&gt;&lt;password xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;admin&lt;/password&gt;&lt;host xmlns=<span class="code-quote">"urn:opendaylight:netconf-node-topology"</span>&gt;127.0.0.1&lt;/host&gt;&lt;/node&gt;&lt;/topology&gt;&lt;/network-topology&gt;&lt;/data&gt;&lt;operation&gt;created&lt;/operation&gt;&lt;/data-change-event&gt;&lt;/data-changed-notification&gt;&lt;/notification&gt; &gt;  </span></pre> </div></div> <p>OK, when we apply <a href="https://jira.opendaylight.org/browse/NETCONF-970" title="Websocket timeout exception " class="issue-link" data-issue-key="NETCONF-970"><del>NETCONF-970</del></a> and <a href="https://jira.opendaylight.org/browse/NETCONF-953" title="Unable to load org.eclipse.jetty.websocket.server.WebSocketServerFactory" class="issue-link" data-issue-key="NETCONF-953"><del>NETCONF-953</del></a> we can make a conclusion that issue is no more present in current ODL releases. eventTime is present in notifications.</p> Blocks MDSAL-282 NETCONF-953 NETCONF-970 Development Rank 0|i037en: