netopeer2-server crashes due to assert failure in lyd_insert_after_node

[yoousra]

netopeer2-v2.7.0-12-g2809ede
sysrepo-v4.2.10-37-gd59ac7e7
libnetconf2-v4.1.2-34-g50defb3
libyang-v4.2.2-105-gb9d150a2a

Hi,

I have a sudden crash of netopeer2-server when performing an "oper get" on an ORAN module that is augmented by a customized leaf which is of type "list" with a different namespace, something like this:
get <yang_oran_module xmlns=yang_oran_namespace><customized_leaf xmlns=customize_namespace/></yang_oran_module>

2026-07-13 06:51:42.560 netopeer2-server(PID:577)[ORU01]: netopeer2-server: /workspace/Services/3rdParty/libyang-v4.2.2-105-gb9d150a2a/src/tree_data.c:670: lyd_insert_after_node: Assertion '!node->next && (node->prev == node) && (sibling != node)' failed.

and we don't receive the reply to the "get".

Would you have an idea about waht could be the reason behind this?

[yoousra]

Hi,

I have an update, it doesn't seem to be related to the fact that we're doing a "get" on an augment, tried it on an non augment leaf and the result is the same. Here's the scenario:

edit-config :

'<performance-measurement-objects xmlns="urn:o-ran:performance-management:1.0">'
        '<epe-measurement-interval>20</epe-measurement-interval>'
        '<epe-measurement-objects>'
        '<measurement-object>CURRENT</measurement-object>'
        '<active>true</active>'
        '<report-info>AVERAGE</report-info>'
        '</epe-measurement-objects>'
        '<epe-measurement-objects>'
        '<measurement-object>VOLTAGE</measurement-object>'
        '<active>true</active>'
        '<report-info>AVERAGE</report-info>'
        '</epe-measurement-objects>'
        '</performance-measurement-objects>'

Then "get" of any list under performance-measurement-objects like get(/o-ran-performance-management:performance-measurement-objects/epe-measurement-objects) => which implies executing our get callback which adds new elements under epe-measurement-objects

Seems like a problem when we've added elements under epe-measurement-objects with our callback and libyang tries to merge this data with the one we've configured before in sysrepo using the edit-config.