https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TRNSPRTPCE-691 transportpce <p>Hello,</p> <p>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.</p> <p> </p> <p>I have attached the karaf log. Please let me know if you need any further details to understand the issue that I'm facing.</p> <p><span class="nobr"><a href="https://jira.opendaylight.org/secure/attachment/18104/18104_karaf.log" title="karaf.log attached to TRNSPRTPCE-691">karaf.log^{<img class="rendericon" src="https://jira.opendaylight.org/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p> </p> <p>From the log it looks like there is issue with osgi framework container like 908-910.</p> <p> </p> <p>I'm not sure if this is right place to report, if not please point me to the right resource.</p> <p> </p> <p>Many thanks for your attention. This is stopping issue, and if it can be addressed sooner, it would a great help!</p> <p> </p> <p>Thanks again for your time</p> <p> </p> TRNSPRTPCE-691

Cannot connect to the netconf (Open ROADM) devices on Chlorine branch (TransportPCE master)

Bug Highest Verified Won't Do Unassigned Balagangadhar Bathula Fri, 23 Sep 2022 14:31:52 +0000 Wed, 16 Nov 2022 14:35:14 +0000 Wed, 16 Nov 2022 14:35:14 +0000 0 3 <p>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.</p> <p>Hello Bala,<br/> Just to be sure, could you just confirm that you are well using the new url in the rfc8040 format to connect TransportPCE to the netconf nodes? (see test_utils.py library)</p> <p>When I tried after changing the URL to the RFC8040, below is the what I see:</p> <p>There is still 404 response.</p> <p> </p> <p>URL used to mount: <a href="http://localhost:8181/rests/config/network-topology:network-topology/topology/topology-netconf/node/" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/rests/config/network-topology:network-topology/topology/topology-netconf/node/</a>&lt;node-name&gt;</p> <p> </p> <p> </p> <p>09:23:42.560 WARN <span class="error">&#91;qtp385743539-923&#93;</span> 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.<br/> 09:23:42.560 WARN <span class="error">&#91;qtp385743539-923&#93;</span> A provider org.opendaylight.restconf.nb.rfc8040.rests.services.impl.RestconfInvokeOperationsServiceImpl 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.RestconfInvokeOperationsServiceImpl will be ignored.<br/> 09:23:42.560 WARN <span class="error">&#91;qtp385743539-923&#93;</span> A provider org.opendaylight.restconf.nb.rfc8040.rests.services.impl.RestconfDataServiceImpl 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.RestconfDataServiceImpl will be ignored.<br/> 09:23:42.561 WARN <span class="error">&#91;qtp385743539-923&#93;</span> A provider org.opendaylight.restconf.nb.rfc8040.rests.services.impl.RestconfStreamsSubscriptionServiceImpl 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.RestconfStreamsSubscriptionServiceImpl will be ignored.<br/> 09:23:42.561 WARN <span class="error">&#91;qtp385743539-923&#93;</span> A provider org.opendaylight.restconf.nb.rfc8040.rests.services.impl.RestconfSchemaServiceImpl 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.RestconfSchemaServiceImpl will be ignored.<br/> 09:23:42.561 WARN <span class="error">&#91;qtp385743539-923&#93;</span> A provider org.opendaylight.restconf.nb.rfc8040.rests.services.impl.RestconfImpl 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.RestconfImpl will be ignored.</p> <p>That should read ".../node=&lt;node-name&gt;" as per <a href="https://www.rfc-editor.org/rfc/rfc8040#section-3.5.3.1" class="external-link" target="_blank" rel="nofollow noopener">list-instance spec</a></p> <p>I fear there is an issue with the url. You should try:</p> <p><font color="#505050"><a href="http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=" class="external-link" target="_blank" rel="nofollow noopener">http://127.0.0.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=</a>&lt;node-name&gt;</font></p> <p>Thanks <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga" class="user-hover" rel="rovarga">rovarga</a> <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=gthouenon" class="user-hover" rel="gthouenon">gthouenon</a> ! Yes, apparently that is an URL issue. i was able to mount devices using the updated URL. Sorry for being naive <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Also can you point me to the APIDOC url? <a href="http://localhost:8181/apidoc/explorer/index.html" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/apidoc/explorer/index.html</a> This doesn't seem to work anymore. I have installed both the odl-mdsal-apidocs and odl-transportpce-swagger.</p> <p>Good news!<br/> It remains to understand now why the apidoc no longer works...</p> <p>I will mark this issue as resolved! Hopefully we can address the API doc issue</p> <p>Oh it's already being marked <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>No Bug. this is in fact due to the migration to RFC 8040 (URL change)</p> Development Rank 0|i042xy:zzr Sprint Sprint 29