[ODLPARENT-33] ssh problems lead to netconf connector problems and bin/client failures Created: 19/May/16 Updated: 24/Jan/18 Resolved: 24/Aug/16 |
|
| Status: | Resolved |
| Project: | odlparent |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Peter Gubka | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5923 |
| Description |
|
https://jenkins.opendaylight.org/bgpcep/job/bgpcep-csit-1node-userfeatures-only-boron/ the problems i ma hitting are the following ones: i use 2) i am unable to configure e.g. bgp peer via netconf connector, because i receive 404 every time i want to use it. I believe this 2 things are related together. |
| Comments |
| Comment by Robert Varga [ 19/May/16 ] |
|
Seems to be karaf-related. |
| Comment by Peter Gubka [ 26/May/16 ] |
|
https://lists.opendaylight.org/pipermail/integration-dev/2016-May/006767.html |
| Comment by Michael Vorburger [ 30/May/16 ] |
|
I've researched this a moment, and found other people having similar issues - it seems to have something to do with exact JDK version and installed JCE providers.. Curiously, I'm not able to easily reproduce this problem locally - are you? E.g. when trying to reproduce this using a Karaf built by https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype as well as a distribution-karaf-0.4.1-Beryllium-SR1 DL'd about 2 months ago, then "./bin/client" works for me. This is on OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14). I doubt an upgrade of OpenJDK from 1.8.0_51 to a 1.8.0_91 helps, but maybe worth a try? What OS are you seeing this on BTW? (NOTE https://github.com/ojdkbuild/ojdkbuild). BTW mine says this, looks like by default it accepts any connection (huh?): Logging in as karaf Or... is this problem specific and only happens when you.. perhaps put your public key SSH into Karaf? Or first enable security, somehow? Are there any specific set up steps / configurations you have taken which we should know about in order to try to reproduce this? PS: I don't see what this 1) error ("NoSuchAlgorithmException: EC KeyPairGenerator not available") could have anything to do with 2) 404.. unless you see the same exception in the log when you access that HTTP, I would suspect these are unrelated. |
| Comment by Ryan Goulding [ 12/Jul/16 ] |
|
Peter, Can you please provide more environmental information surrounding how to reproduce this? If not, I am tempted to say we resolve this as invalid... it appears to be related to your build environment. That said, we are happy to make recommendations surrounding what works best for ODL environment setup. Regards, |
| Comment by Michael Vorburger [ 12/Jul/16 ] |
|
Luis Gomez knows more about this, see email thread "Re: [integration-dev] bin/client advice", and https://issues.apache.org/jira/browse/KARAF-4502 .. |
| Comment by Ryan Goulding [ 12/Jul/16 ] |
|
Okay JCE related. Thanks Michael... looks like if we upgrade to karaf 3.0.7 we could kill this bug too. Setting to confirmed. |
| Comment by Peter Gubka [ 13/Jul/16 ] |
|
(In reply to Ryan Goulding from comment #4) Hi. |
| Comment by Ryan Goulding [ 09/Aug/16 ] |
| Comment by Vratko Polak [ 24/Aug/16 ] |
|
Re-opening as this appeared on Boron autorelease builds (not snapshots, frustrating). |
| Comment by Vratko Polak [ 24/Aug/16 ] |
|
Oops, sorry. Turns out that build is from before Karaf upgrade to 3.0.7 was merged. |