"/notif:notification" not found error on connecting

[ss8-suzushun]

[version information] netopeer2 : 2.0.77 libnetconf2 : 2.1.20 libyang : 2.46.3 sysrepo : 2.2.150

Hi, When connect is executed, the following message is output and the connection does not succeed. The same thing is happening with callhome. How do you solve this error?

・connect

$ netopeer2-cli
load_config: No saved configuration.
> connect --host 172.27.127.21 --login john
john@172.27.127.21 password:
　…
ly ERROR: Augment target node "/notif:notification" from module "yuma-system" was not found. (Path "/yuma-system:{augment='/notif:notification'}".)
cmd_connect: Connecting to the 172.27.127.21:830 as user "john" failed.

・listen

> listen --host 0.0.0.0 --timeout 800 --login john
Waiting 800s for an SSH Call Home connection on port 4334...
The authenticity of the host '172.27.127.21' cannot be established.
ssh-ed25519 key fingerprint is XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX.
Are you sure you want to continue connecting (yes/no)? yes
john@172.27.127.21 password:
　…
ly ERROR: Augment target node "/notif:notification" from module "yuma-system" was not found. (Path "/yuma-system:{augment='/notif:notification'}".)
cmd_listen: Receiving SSH Call Home on port 4334 as user "john" failed.
>

[michalvasko]

You have quite a mix of the versions, latest libyang and sysrepo and ancient libnetconf2 and netopeer2, which may be a problem on its own. As for the issue, can you provide yuma-system.yang the server is using?

[ss8-suzushun]

thank you for your response yuma-system.yang.txt

[michalvasko]

Right, the container it is targeting does not exist in our version of the notifications module because it causes YANG validation to fail. In general, the container is not used and is just a template, sort-of, for notifications (the module is really old and an attempt to transform XML Schema definition to YANG).

Having the whole context, I am not sure how to fix it. One hack would be to modify this YANG module locally (in the client search directory) and remove this augment.

EDIT: Actually, I am checking whether the container cannot be uncommented because it was a long time it has caused problems and it may no longer be the case.

[michalvasko]

Okay, I have modified the module and if you install the latest netopeer2, you should no longer get the error.

[ss8-suzushun]

I have confirmed that the issue is resolved. Thank you : )