[NETCONF-1065] Wrong Map Node type causes Yanglib data merge failure Created: 22/Jun/23  Updated: 29/Jun/23  Resolved: 29/Jun/23

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: 6.0.0, 5.0.7, 4.0.9

Type: Bug Priority: Medium
Reporter: Ruslan Kashapov Assignee: Ruslan Kashapov
Resolution: Done Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File karaf.log.tar.gz    
Issue Links:
Relates
relates to NETCONF-1068 YangLib: missing mandatory descendant... Open

 Description   

The issue caused by SchemaContextHandler (restconf-nb) responsible for setting up the yanglib data ("ietf-yang-library:modules-state"). The data is being assembled as normalized node with explicit setting of modules (submodules) list node as ordered map node.

On yanglib service data merge the same entities are passed as binded objects, resulting map associated nodes being unordered (as defined in schema). Mapping node type difference causes data merge failure with exception like below (full log attached)

java.lang.IllegalArgumentException: Require interface org.opendaylight.yangtools.yang.data.api.schema.SystemMapNode, got ImmutableUserMapNode...

STR:

  • start karaf
  • feature:install odl-yanglib
  • copy any yang file to karaf_home/cache/schema
  • restart karaf

Generated at Wed Feb 07 20:16:35 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.