[CONTROLLER-1370] APIdoc explorer URLs contain extra 'node' in REST calls Created: 12/Jun/15  Updated: 03/May/18  Resolved: 02/Jun/16

Status: Resolved
Project: controller
Component/s: restconf
Affects Version/s: Lithium
Fix Version/s: None

Type: Bug
Reporter: Carol Sanders Assignee: Ryan Goulding
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: PDF File APIdoc-explorer.pdf    
Issue Links:
Duplicate
is duplicated by NETCONF-61 Mountpoint URI of Autogenerated RestC... Resolved
External issue ID: 3708

 Description   

When browsing the Controller-config API in APIdoc explorer
The provided url for REST POST, GET, PUT, and DELETE calls contain an extra 'node' designation in the url which results in error

{
"errors": {
"error": [

{ "error-type": "protocol", "error-tag": "unknown-element", "error-message": "\"controller-config\" in URI was not found in parent data node" }

]
}
}

Steps to reproduce
1. Download latest Lithium
2. Start controller and install odl-netconf-all, odl-restconf-all
3. Open APIdoc explorer
4. Browse to Mounted devices/controller-config
5. select ietf-netconf-monitoring

http://localhost:8181/restconf/operational/opendaylight-inventory:nodes/node/node/controller-config/yang-ext:mount/ietf-netconf-monitoring:netconf-state/



 Comments   
Comment by Carol Sanders [ 12/Jun/15 ]

Attachment APIdoc-explorer.pdf has been added with description: screenshot of APIdoc explorer

Comment by Jan Hajnar [ 25/Jun/15 ]

patch:
https://git.opendaylight.org/gerrit/#/c/23267/

Comment by Alexis de Talhouƫt [ 14/Apr/16 ]

NETCONF master --> https://git.opendaylight.org/gerrit/#/c/37631/

Comment by Tomas Cere [ 17/May/16 ]

Fixed in BE, there will be no more lithium sr's

Comment by Ryan Goulding [ 02/Jun/16 ]

boron: https://git.opendaylight.org/gerrit/#/c/37631/

beryllium: https://git.opendaylight.org/gerrit/#/c/37731/

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