[NETCONF-573] Mountpoint created using mdsal DOM API can't be reached by restconf Created: 05/Oct/18  Updated: 20/Nov/18  Resolved: 20/Nov/18

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: Neon
Fix Version/s: Neon

Type: Bug Priority: Medium
Reporter: Richard Kosegi Assignee: Jakub Morvay
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Master branch (neon)

restconf version 1.9.0-SNAPSHOT


Issue Links:
Duplicate
duplicates CONTROLLER-1869 DOMMountPointService needs to perform... Resolved

 Description   

In jsonrpc project, we are creating mountpoints using

 

final DOMMountPointService.DOMMountPointBuilder mountBuilder = mountService.createMountPoint(biPath);

mountBuilder.addService(DOMDataBroker.class, rpcDataBroker);

we recently switched to md-sal version of DOMDataBroker (previously org.opendaylight.controller.md.sal.dom.api.DOMDataBroker - it is deprecated for a while)

 

Now I can't access that using restconf, eg :

PUT http://localhost:8181/restconf/config/jsonrpc:config/configured-endpoints/something/yang-ext:mount/prefix:something/xyz

2018-10-05 15:23:26,661 | WARN  | tp1336482246-114 | BrokerFacade                     | 268 - org.opendaylight.netconf.restconf-nb-bierman02 - 1.9.0.SNAPSHOT | DOM data broker service is not available for mount point /(some-namespace?revision=2018-09-08)something/[\{(some-namespace?revision=2018-09-08)entity=xyz}]

 

Problem seems to be that BrokerFacade is checking for "old" API only:

 

 33 import org.opendaylight.controller.md.sal.dom.api.DOMDataBroker;

...

 275         final Optional<DOMDataBroker> domDataBrokerService = mountPoint.getService(DOMDataBroker.class);

 

Is there something we can do or should we switch back to deprecated API?

 

 



 Comments   
Comment by Jakub Morvay [ 20/Nov/18 ]

Although, this was reported before CONTROLLER-1869, marking this issue as duplicate of the controller issue since it has better description.

Anyway, your issue should be fixed now.

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