[MDSAL-709] Some RPCs are not accessible internally Created: 29/Nov/21  Updated: 30/Nov/21  Resolved: 30/Nov/21

Status: Resolved
Project: mdsal
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Olivier Dugeon Assignee: Robert Varga
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File karaf.log    

 Description   

I'm trying to call RPCs within a java class and I got errors reporting that RPCs are not registered. However, these inaccessible RPCs are part of a pack of 6 which are all registered in the same place and, at least, one of them is accessible.

I attached a karaf.log to illustrate my purpose. Code is available here https://git.opendaylight.org/gerrit/c/bgpcep/+/97076 and more precisely in https://git.opendaylight.org/gerrit/c/bgpcep/+/97076/6/pcep/server/server-provider/src/main/java/org/opendaylight/bgpcep/pcep/server/provider/ManagedTePath.java line 274 for addPath which is OK, line 370 for updatePath which failed and 403 for removePath which failed too.

Not that all of these RPCs are working pretty well through RESTCONF using rest API interface.



 Comments   
Comment by Olivier Dugeon [ 30/Nov/21 ]

Well, there is not problem on MD-SAL. The problem come from the fact that I forgot to add the mandatory Topology Reference in the input argument of Update LSP and Remove LSP RPCs. Thus, MD-SAL was unable to retrieve the correct RPCs as they are registered for a given Topology Reference and not for all. Same problem occurs if you use the Restconf API. But, this time, as the mandatory parameter is not provided, Restconf API explicitly report the problem.

Thus, I close this issue.

Comment by Olivier Dugeon [ 30/Nov/21 ]

Well, there is not problem on MD-SAL. The problem come from the fact that I forgot to add the mandatory Topology Reference in the input argument of Update LSP and Remove LSP RPCs. Thus, MD-SAL was unable to retrieve the correct RPCs as they are registered for a given Topology Reference and not for all. Same problem occurs if you use the Restconf API. But, this time, as the mandatory parameter is not provided, Restconf API explicitly report the problem.

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