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-614 netconf <p>As shown here this regression has been introduced very recently:</p> <p><a href="https://jenkins.opendaylight.org/releng/job/netconf-csit-1node-callhome-only-neon/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/netconf-csit-1node-callhome-only-neon/</a></p> <p>The operational info just shows DISCONNECTED:</p> <p>/restconf/operational/odl-netconf-callhome-server:netconf-callhome-server</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> { <span class="code-quote">"netconf-callhome-server"</span>: { <span class="code-quote">"allowed-devices"</span>: { <span class="code-quote">"device"</span>: [ { <span class="code-quote">"unique-id"</span>: <span class="code-quote">"netopeer"</span>, <span class="code-quote">"callhome-status:device-status"</span>: <span class="code-quote">"DISCONNECTED"</span>, <span class="code-quote">"ssh-host-key"</span>: <span class="code-quote">"AAAAB3NzaC1yc2EAAAADAQABAAABAQDF2UazsHh/amdGT2xpmn5rpSrybUl66cic082NMRS5qEyVyTc8mvgzj4m1gXP/cVOJmZ6TR9AxCUcNnc7MZMpemg4n0kawM4wwwWP43Z46UG342Dz1B1yCgi9WTzsF7/6J1d57xNYIVmX6IQBhg+hbglyM4L658mM22ZkZuWw2AMbMK46HFbRIfwjoqziFi8jjJWU5WtZL5YpCofRb9PkRuH/ejxs/NJXgKA9vEOf8pXQJ8bGNa8WKHBBqidaRdOWa7EMGPIr6bApzN4P/jiY1m3uodaVI64WOg88oc9h1RP6gvJkN8eSBFFLVNuyOgxyNpxXTAyJ84mlTJgDVfmF7"</span> } ] } } } </pre> </div></div> <p>Karaf log shows this WARN:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 2019-05-06T10:33:39,798 | WARN | nioEventLoopGroup-4-2 | DefaultAuthFuture | 132 - org.apache.sshd.osgi - 2.2.0 | notifyListener(DefaultAuthFuture[id=ssh-connection][value=org.apache.sshd.common.SshException: No more authentication methods available]) failed (NullPointerException) to invoke org.opendaylight.netconf.callhome.protocol.NetconfCallHomeServer$2@600d8dea: <span class="code-keyword">null</span> </pre> </div></div> <p>When it worked I can see this instead:</p> <p>/restconf/operational/odl-netconf-callhome-server:netconf-callhome-server</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> { <span class="code-quote">"netconf-callhome-server"</span>: { <span class="code-quote">"allowed-devices"</span>: { <span class="code-quote">"device"</span>: [ { <span class="code-quote">"unique-id"</span>: <span class="code-quote">"netopeer"</span>, <span class="code-quote">"callhome-status:device-status"</span>: <span class="code-quote">"FAILED_AUTH_FAILURE"</span>, <span class="code-quote">"ssh-host-key"</span>: <span class="code-quote">"AAAAB3NzaC1yc2EAAAADAQABAAABAQDF2UazsHh/amdGT2xpmn5rpSrybUl66cic082NMRS5qEyVyTc8mvgzj4m1gXP/cVOJmZ6TR9AxCUcNnc7MZMpemg4n0kawM4wwwWP43Z46UG342Dz1B1yCgi9WTzsF7/6J1d57xNYIVmX6IQBhg+hbglyM4L658mM22ZkZuWw2AMbMK46HFbRIfwjoqziFi8jjJWU5WtZL5YpCofRb9PkRuH/ejxs/NJXgKA9vEOf8pXQJ8bGNa8WKHBBqidaRdOWa7EMGPIr6bApzN4P/jiY1m3uodaVI64WOg88oc9h1RP6gvJkN8eSBFFLVNuyOgxyNpxXTAyJ84mlTJgDVfmF7"</span> } ] } } } </pre> </div></div> <p>And in the Karaf log:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 2019-04-30T15:43:31,011 | INFO | nioEventLoopGroup-4-2 | CallhomeStatusReporter | 276 - org.opendaylight.netconf.callhome-provider - 1.6.1 | Setting auth failed status <span class="code-keyword">for</span> callhome device id:netopeer. </pre> </div></div> NETCONF-614

Netconf callhome server does not publish disconnect cause

Bug Medium Resolved Done Robert Varga Luis Gomez Mon, 6 May 2019 17:35:54 +0000 Tue, 7 May 2019 08:28:53 +0000 Tue, 7 May 2019 08:28:53 +0000 Neon SR1 Sodium Neon SR1 Sodium netconf 0 2 <p>This looks like the public key is not available after auth failure, hence NetconfCallHomeServer:144 will acquire a null and then it goes sideways. The same think is happening in Sodium.</p> <p>Furthermore it seems device.getSshHostKey() is getting to be null for some reason. Grrr, gotta love this code <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/sad.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Actually, this seems to be the primary cause:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>    @Override     public void reportFailedAuth(final PublicKey sshKey) {         AuthorizedKeysDecoder decoder = new AuthorizedKeysDecoder();         for (Device device : getDevicesAsList()) {             String keyString = device.getSshHostKey();             try {                 PublicKey pubKey = decoder.decodePublicKey(keyString);                 if (sshKey.getAlgorithm().equals(pubKey.getAlgorithm()) &amp;&amp; sshKey.equals(pubKey)) { </pre> </div></div> <p>if keyString is null, decodePublicKey() will fail on it.</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> can you check if we are getting warnings introduced by the proposed patch. Would it possible to dump config/oper DS in the errored case?</p> <p>Just added oper info when it fails vs when it works.</p> <p>The DTCL NPEs are present even in successful runs – opened <a href="https://jira.opendaylight.org/browse/NETCONF-615" title="Callhome throws NPEs in DTCL" class="issue-link" data-issue-key="NETCONF-615"><del>NETCONF-615</del></a> to track them.</p> <p>This is the root cause: kex is not available, as it will be torn down immediately after KeyEstablished event, hence it must be captured before the callback returns.</p> Development Rank 0|i03nof: