karaf.log
[TRNSPRTPCE-691] Cannot connect to the netconf (Open ROADM) devices on Chlorine branch (TransportPCE master) Created: 23/Sep/22 Updated: 16/Nov/22 Resolved: 16/Nov/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Highest |
| Reporter: | Balagangadhar Bathula | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
karaf.log
|
| Description |
|
Hello, I using the TransportPCE master branch (I presume it is on Chlorine) version. However none of the device are getting mounted on the controller. I get an 404 error response when trying to mount. To check if I was doing anything wrong, I have used Sulfur version of TransportPCE and everything works as expected.
I have attached the karaf log. Please let me know if you need any further details to understand the issue that I'm facing.
From the log it looks like there is issue with osgi framework container like 908-910.
I'm not sure if this is right place to report, if not please point me to the right resource.
Many thanks for your attention. This is stopping issue, and if it can be addressed sooner, it would a great help!
Thanks again for your time
|
| Comments |
| Comment by Robert Varga [ 23/Sep/22 ] |
|
Aside from the installation-time exception I do not see anything untoward. I am no expert on tpce, though, so someone from the transportpce team needs to take a look. |
| Comment by Gilles Thouenon [ 26/Sep/22 ] |
|
Hello Bala, |
| Comment by Balagangadhar Bathula [ 26/Sep/22 ] |
|
When I tried after changing the URL to the RFC8040, below is the what I see: There is still 404 response.
URL used to mount: http://localhost:8181/rests/config/network-topology:network-topology/topology/topology-netconf/node/<node-name>
09:23:42.560 WARN [qtp385743539-923] A provider org.opendaylight.restconf.nb.rfc8040.rests.services.impl.RestconfOperationsServiceImpl registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.opendaylight.restconf.nb.rfc8040.rests.services.impl.RestconfOperationsServiceImpl will be ignored. |
| Comment by Robert Varga [ 26/Sep/22 ] |
|
That should read ".../node=<node-name>" as per list-instance spec |
| Comment by Gilles Thouenon [ 26/Sep/22 ] |
|
I fear there is an issue with the url. You should try: http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=<node-name> |
| Comment by Balagangadhar Bathula [ 26/Sep/22 ] |
|
Thanks rovarga gthouenon ! Yes, apparently that is an URL issue. i was able to mount devices using the updated URL. Sorry for being naive Also can you point me to the APIDOC url? http://localhost:8181/apidoc/explorer/index.html This doesn't seem to work anymore. I have installed both the odl-mdsal-apidocs and odl-transportpce-swagger. |
| Comment by Gilles Thouenon [ 26/Sep/22 ] |
|
Good news! |
| Comment by Balagangadhar Bathula [ 26/Sep/22 ] |
|
I will mark this issue as resolved! Hopefully we can address the API doc issue |
| Comment by Balagangadhar Bathula [ 26/Sep/22 ] |
|
Oh it's already being marked |
| Comment by Olivier Renais [ 16/Nov/22 ] |
|
No Bug. this is in fact due to the migration to RFC 8040 (URL change) |
