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/NETCONF-574 netconf <p>When a rogue device (it is not added in whitelist) tries to connect to controller (callhome server), it fails to connect (OK) but the device status "FAILED_NOT_ALLOWED" does not show in the callhome server API (NOK):</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> GET /restconf/operational/odl-netconf-callhome-server:netconf-callhome-server 404 {<span class="code-quote">"errors"</span>:{<span class="code-quote">"error"</span>:[{<span class="code-quote">"error-type"</span>:<span class="code-quote">"application"</span>,<span class="code-quote">"error-tag"</span>:<span class="code-quote">"data-missing"</span>,<span class="code-quote">"error-message"</span>:<span class="code-quote">"Request could not be completed because the relevant data model content does not exist "</span>}]}} </pre> </div></div> <p>In the karaf log it can be seen:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 2018-10-09T09:34:13,471 | INFO | remote-connector-processing-executor-11 | NetconfDevice | 287 - org.opendaylight.netconf.sal-netconf-connector - 1.8.1.SNAPSHOT | RemoteDevice{netopeer}: Netconf connector initialized successfully 2018-10-09T09:34:13,474 | WARN | opendaylight-cluster-data-notification-dispatcher-48 | CallhomeStatusReporter | 268 - org.opendaylight.netconf.callhome-provider - 1.5.1.SNAPSHOT | No corresponding callhome device found - exiting. </pre> </div></div> <p>So maybe this is expected behavior.</p> <p>In any case the failing test has been commented in this patch:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/76807" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/76807</a></p> NETCONF-574

No status for rogue device in callhome server API

Bug Medium In Progress Unresolved Manoj Chokka Luis Gomez Tue, 9 Oct 2018 20:19:18 +0000 Tue, 2 Jun 2020 17:07:21 +0000 0 3 <p>I've just quickly ran trough the implementation and it seems that the device should be reported as FAILED_NOT_ALLOWED.</p> <p>Need to investigate it further why it is not reported that way.</p> <p>Update on the analysis done so far,</p> <ul> <li>The code does not have any issues.</li> <li>During manual testing we were not able to reproduce the issue. We were able to see the message FAILED_NOT_ALLOWED in the device status for rouge devices.</li> <li>Upon examination of the callhome.robot test case, we found the "apt-get update" is taking more time than expected. But the wait time for the test case is only 30s. This is the reason the test case is failing.</li> <li>A simple timeout change would do the trick.</li> </ul> <p> </p> <p>I will fix this in the CSIT.</p> <p>Hi Luis,</p> <p>Found a better fix for the testcase.</p> <p>Looks like the entries in sources.list in the docker are working a few times and failing the other times.</p> <p>Found the actual sources list at <a href="https://wiki.debian.org/LTS/Using" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.debian.org/LTS/Using</a></p> <p>deb <a href="http://deb.debian.org/debian/" class="external-link" target="_blank" rel="nofollow noopener">http://deb.debian.org/debian/</a> jessie main contrib non-free</p> <p>deb-src <a href="http://deb.debian.org/debian/" class="external-link" target="_blank" rel="nofollow noopener">http://deb.debian.org/debian/</a> jessie main contrib non-free </p> <p>deb <a href="http://security.debian.org/" class="external-link" target="_blank" rel="nofollow noopener">http://security.debian.org/</a> jessie/updates main contrib non-free</p> <p>deb-src <a href="http://security.debian.org/" class="external-link" target="_blank" rel="nofollow noopener">http://security.debian.org/</a> jessie/updates main contrib non-free</p> <p> </p> <p>To reflect these changes,</p> <ul> <li>create sources.list file in ~/integration-test/csit/variables/netconf/callhome</li> <li>add the above sources to the file.</li> <li>add a volume in docker-compose.yaml file, <ul> <li>-   /home/chokkma/integration-test/csit/variables/netconf/callhome/sources.list:/etc/apt/sources.list</li> </ul> </li> <li>the above volume command will copy the new source.list to the /etc/apt/sources.list</li> </ul> <p>And we also need to change the timeout in to 300s in callhome.robot, to allow 'apt-get update' and 'apt-get install curl' to finish successfully.</p> <p> </p> <p>If you approve these changes, I can make the changes and push them.</p> <p>Please let me know.</p> <p> </p> <p>BR</p> <p>Manoj</p> <p> </p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=cmanoj" class="user-hover" rel="cmanoj">cmanoj</a>, per the conversation we had in the kernel call today is the "fix" for this issue<br/> going to all happen on the test side of things? If so, we can move this ticket to that project.<br/> let me know and I can take care of that.</p> Development Rank 0|i03jgf: