[NETCONF-218] "odl-netconf-mdsal" or "odl-netconf-clustered-topology" breaks feature:install in karaf client Created: 10/Jun/16  Updated: 15/Mar/19  Resolved: 17/Oct/16

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jozef Behran Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File karaf.log.xz    
External issue ID: 6045

 Description   

Tested on latest Boron.

1. Extract bare ODL; cd to the distribution; run bin/start.
2. sshpass -pkaraf bin/client feature:install odl-restconf
3. sshpass -pkaraf bin/client feature:install odl-clustering-test-app
4. sshpass -pkaraf bin/client feature:install odl-netconf-mdsal
5. sshpass -pkaraf bin/client feature:install odl-netconf-connector-all

The command 5 will be rejected with "Failed to get the session".

The same happens if in step 3 you say "odl-netconf-mdsal".

However the sequence works when you run "bin/karaf" at the step 1 and enter the "feature:install" commands at the karaf console prompt instead of using the karaf client.

The logs show "Duplicate interface name in class file Proxy

{some_GUID_here}

" (see attached file).

 Comments   
Comment by Jozef Behran [ 10/Jun/16 ]

Attachment karaf.log.xz has been added with description: karaf.log from the steps described in the description

Comment by Tomas Cere [ 13/Jun/16 ]

(In reply to Jozef Behran from comment #0)
> Created attachment 1037 [details]
> karaf.log from the steps described in the description
>
> Tested on latest Boron.
>
> 1. Extract bare ODL; cd to the distribution; run bin/start.
> 2. sshpass -pkaraf bin/client feature:install odl-restconf
> 3. sshpass -pkaraf bin/client feature:install odl-clustering-test-app
> 4. sshpass -pkaraf bin/client feature:install odl-netconf-mdsal
> 5. sshpass -pkaraf bin/client feature:install odl-netconf-connector-all
>

I just tried and I couldn't reproduce this. Are you installing the features one after another without leaving any time to actually finish installing the previous feature?

> The command 5 will be rejected with "Failed to get the session".
>
This suggests that karaf is still busy with the previous feature since this
is just a failure from the client script.

>
> The logs show "Duplicate interface name in class file Proxy

{some_GUID_here}

"
> (see attached file).
Unrelated

Comment by Vratko Polak [ 17/Oct/16 ]

I think I figured this one out.

By default, the described 5 step procedure works.
But if user has exported KARAF_REDIRECT environment variable, pointing to a file in a directory which does not exist yet ($KARAF_HOME/data/log/ for example),
bin/start fails without any message, and of course client cannot connect when no ODL is running.

Generated at Wed Feb 07 20:14:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.