netopeer2 icon indicating copy to clipboard operation
netopeer2 copied to clipboard

Notifications of internal module "sysrepo" cannot be subscribed to

Open rydy opened this issue 1 year ago • 1 comments

Hi, I'm using version 2.2.31, By subscribing to the netopper2-cli for all notifications, the following error occurs, which was not present in previous versions.

netopper2-cli log:

 subscribe --filter-xpath /*
ERROR
        type:     application
        tag:      operation-failed
        severity: error
        message:  Notifications of internal module "sysrepo" cannot be subscribed to.

        type:     application
        tag:      operation-failed
        severity: error
        message:  User callback failed.

netopper2-server log:

[2024-10-25 08:18:54.626] [DBG]: LN: Session 21: Received message:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="51"><create-subscription xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"><filter type="xpath" select="/*"/></create-subscription></rpc>

[2024-10-25 08:18:54.631] [ERR]: SR: Notifications of internal module "sysrepo" cannot be subscribed to.
[2024-10-25 08:18:54.631] [WRN]: SR: EV ORIGIN: "/notifications:create-subscription" "rpc" ID 23 priority 0 failed (Operation not supported).
[2024-10-25 08:18:54.631] [ERR]: SR: User callback failed.
[2024-10-25 08:18:54.631] [ERR]: NP: Failed to send an RPC (User callback failed).
[2024-10-25 08:18:54.631] [DBG]: LN: Session 21: Sending message:

#537


[2024-10-25 08:18:54.631] [DBG]: LN: Session 21: Sending message:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="51"><rpc-error><error-type>application</error-type><error-tag>operation-failed</error-tag><error-severity>error</error-severity><error-message xml:lang="en">Notifications of internal module "sysrepo" cannot be subscribed to.</error-message></rpc-error><rpc-error><error-type>application</error-type><error-tag>operation-failed</error-tag><error-severity>error</error-severity><error-message xml:lang="en">User callback failed.</error-message></rpc-error></rpc-reply>

[2024-10-25 08:18:54.631] [DBG]: LN: Session 21: Sending message:

##


[2024-10-25 08:18:54.632] [INF]: NP: Session 21: thread 1 event new RPC.
[2024-10-25 08:18:54.632] [INF]: NP: Session 21: thread 1 event reply error.

rydy avatar Oct 25 '24 08:10 rydy