[NEUTRON-153] Neutron NB API feature fails to install when combining with odl-mdsal-trace Created: 09/Jan/18  Updated: 26/Feb/18  Resolved: 26/Feb/18

Status: Verified
Project: neutron
Component/s: northbound-api
Affects Version/s: Oxygen
Fix Version/s: Oxygen

Type: Bug Priority: Medium
Reporter: Jamo Luhrsen Assignee: Michael Vorburger
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File odl1_karaf.log    
Issue Links:
Blocks
blocks NETVIRT-878 CSIT should help to detect possible m... In Progress

 Description   

I am not sure which project to assign this bug, so starting with neutron. Please move it
as needed.

to recreate:

  • start karaf
  • feature:install odl-mdsal-trace
  • feature:install --no-auto-refresh odl-infrautils-ready odl-netvirt-openstack

at this point, once features have loaded it seems that neutron NB is not working.

This is in the karaf.log:

2018-01-08 19:00:27,797 | WARN | ender-2-thread-1 | AbstractLifeCycle | 282 - org.eclipse.jetty.util - 9.2.21.v20170120 | FAILED HttpServiceContext ... httpContext=WebAppHttpContext ... org.opendaylight.neutron.northbound-api - 374 ... java.lang.NoClassDefFoundError: javax/ws/rs/ext/MessageBodyReader java.lang.NoClassDefFoundError: javax/ws/rs/ext/MessageBodyReader

And in an openstack integration, you can see that neutron itself is getting 404
responses.



 Comments   
Comment by Jamo Luhrsen [ 09/Jan/18 ]

attached is a full karaf.log from a CSIT job that installed features as described.

Comment by Michael Vorburger [ 09/Jan/18 ]

I'll try to locally reproduce this some time (timeframe comings weeks, not tomorrow), to see if I get what's going on...

skitt do you think your upcoming CONTROLLER-1764 fix could have anything to do with and help for this problem?

Comment by Michael Vorburger [ 26/Feb/18 ]

jluhrsen seeing NETVIRT-878 moving, it seems to me that this is no longer an issue blocking you and was apparently fixed in Oxygen - do you confirm, and OK to close this issue?

Comment by Jamo Luhrsen [ 26/Feb/18 ]

well, NETVIRT-878 is moving because I'm using featuresBoot.

but, I just tried this on latest Oxygen and I think it's ok now. At least I got a 200 response using a neutron NB API and
I did not see that NoClassDefFoundError in the log.

However, there was a big mess of something going on. something with netconf and beir?

here's the karaf console:

opendaylight-user@root>feature:install --no-auto-refresh odl-infrautils-ready odl-netvirt-openstack                                    
Error executing command: Error restarting bundles:
    Could not resolve module: org.opendaylight.netconf.restconf-nb-bierman02 [381]
  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.opendaylight.netconf.restconf-nb-bierman02 [osgi.identity; osgi.identity="org.opendaylight.netconf.restconf-nb-bierman02"; type="osgi.bundle"; version:Version="1.7.0.SNAPSHOT"] because it is exposed to package 'javax.annotation' from resources javax.annotation-api [osgi.identity; osgi.identity="javax.annotation-api"; type="osgi.bundle"; version:Version="1.2.0"] and org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.11.3.v20170209-1843"; singleton:="true"] via two dependency chains.

Chain 1:
  org.opendaylight.netconf.restconf-nb-bierman02 [osgi.identity; osgi.identity="org.opendaylight.netconf.restconf-nb-bierman02"; type="osgi.bundle"; version:Version="1.7.0.SNAPSHOT"]
    import: (osgi.wiring.package=javax.annotation)
     |
    export: osgi.wiring.package: javax.annotation
  javax.annotation-api [osgi.identity; osgi.identity="javax.annotation-api"; type="osgi.bundle"; version:Version="1.2.0"]

Chain 2:
  org.opendaylight.netconf.restconf-nb-bierman02 [osgi.identity; osgi.identity="org.opendaylight.netconf.restconf-nb-bierman02"; type="osgi.bundle"; version:Version="1.7.0.SNAPSHOT"]
    import: (&(osgi.wiring.package=com.google.common.base)(&(version>=23.3.0)(!(version>=24.0.0))))
     |
    export: osgi.wiring.package=com.google.common.base; uses:=javax.annotation
  com.google.guava [osgi.identity; osgi.identity="com.google.guava"; type="osgi.bundle"; version:Version="23.3.0.jre"]
    import: (osgi.wiring.package=javax.annotation)
     |
    export: osgi.wiring.package: javax.annotation
  org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.11.3.v20170209-1843"; singleton:="true"]
opendaylight-user@root>Unsatisfied Requirements:                                                                                       
osgi.wiring.package; filter:="(osgi.wiring.package=org.opendaylight.netconf.sal.rest.api)"
osgi.wiring.package; filter:="(osgi.wiring.package=org.opendaylight.netconf.sal.restconf.api)"
Unsatisfied Requirements:
osgi.wiring.package; filter:="(osgi.wiring.package=org.opendaylight.netconf.sal.rest.api)"
osgi.wiring.package; filter:="(osgi.wiring.package=org.opendaylight.netconf.sal.restconf.api)"
Unsatisfied Requirements:

 

    1. these above lines with osgi.wiring.package keep repeating for a while.

 

 

Comment by Jamo Luhrsen [ 26/Feb/18 ]

closing this as I filed a new issue for the beirman02 problem.

 https://jira.opendaylight.org/browse/NETCONF-516

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