[TRNSPRTPCE-702] Lightynode : Issue with Serializataion/Deserialization of notifications Created: 21/Nov/22 Updated: 16/Mar/23 Resolved: 16/Mar/23 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | High |
| Reporter: | Christophe BETOULE | Assignee: | Christophe BETOULE |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 3 weeks, 1 day | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Lightynode |
| Description |
|
When Lightynode generates notifications, the serialization process of the org-openroadm-device change-notification notification does not insert the namespace in the <edit> body.
Lightynode trace: <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
Honeynode trace: <?xml version="1.0" encoding="utf-8"?>
|