[CONTROLLER-214] problem to use slashes as identifier behind mount point Created: 14/Mar/14 Updated: 25/Jul/23 Resolved: 02/Apr/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | restconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Gloncak | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| Attachments: |
|
| External issue ID: | 524 |
| Description |
|
Email from Giles Heron: I'm trying to do a GET on a RESTCONF URL in ODL. if I go to e.g. http://172.23.29.120:8080/restconf/config/opendaylight-inventory:nodes/node/xrvr-a/yang-ext:mount/Cisco-IOS-XR-ifmgr-cfg:interface-configurations/interface-configuration/act/Loopback0 then it works ok. But if I want to get the config of a GigE interface, e.g. GigabitEthernet0/0/0/0 I hit a problem. I've tried to use %2F instead of the "/". so I do a get on: I get no response from ODL. And no error log either. If I deliberately put a non-existent interface in I'll get "No data exists" if the interface name (e.g. "Loopback4") is feasible or an HTTP 500 error if it isn't (e.g. "foo"). am I doing something wrong? Or is this a bug? |
| Comments |
| Comment by Jozef Gloncak [ 14/Mar/14 ] |
|
Attachment opendaylight.zip has been added with description: opendaylight.log |
| Comment by Jozef Gloncak [ 14/Mar/14 ] |
|
I tried insert data with key like GigabitEthernet0%2F0%2F0%2F0 before mount point and there was no problem. Giles also sent his opendaylight.log file (see atachements) |
| Comment by Giles Heron [ 01/Apr/14 ] |
|
Hi, is it possible for someone to look at this? We can't progress some of our testing until it's fixed |
| Comment by Jozef Gloncak [ 02/Apr/14 ] |
|
getDataWithSlashesBehindMountPoint() test was added to sal-rest-connector and is passing. Maybe problem is during getting data. |
| Comment by Giles Heron [ 02/Apr/14 ] |
|
seems to be fixed in latest stable SP build. thanks! I must have been testing on an earlier build when I raised this. |