[CONTROLLER-958] Helium distro: Error executing command: No feature named 'transaction' with version '0.0.0' available Created: 27/Oct/14  Updated: 19/Oct/17  Resolved: 11/Nov/15

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: Helium
Fix Version/s: None

Type: Bug
Reporter: chandralekha Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC


External issue ID: 2257
Priority: Highest

 Description   

I downloaded the distribution-karaf-0.2.0-Helium.zip and unzipped it to run ./bin/karaf and am getting error while installing some features.

opendaylight-user@root>feature:install odl-ovsdb-openstack odl-ovsdb-northbound odl-restconf odl-mdsal-apidocs odl-adsal-all odl-adsal-northbound odl-dlux-core Error executing command: No feature named 'transaction' with version '0.0.0' available

While debugging : Observed that transaction feature is depending on odl-adsal-clustering

opendaylight-user@root>feature:info odl-adsal-clustering
Feature odl-adsal-clustering 0.5.1-Helium
Description:
OpenDaylight :: AD-SAL :: Clustering
Feature has no configuration
Feature has no configuration files
Feature depends on:
transaction 0.0.0
odl-base-felix-dm 0.0.0
odl-base-eclipselink-persistence 0.0.0
odl-adsal-core 0.8.1-Helium
Feature contains followed bundles:
mvn:org.opendaylight.controller/clustering.services/0.5.1-Helium
mvn:org.opendaylight.controller/clustering.services-implementation/0.4.3-Helium
Feature has no conditionals.

Environment: Ubuntu version: 14.04; Java version: 1.7

Workaround:
1. Downloaded the controller(master branch) source code and performed mvn clean install.
2. Download jta-1.0.1B.jar http://download.java.net/maven/2/javax/transaction/jta/1.0.1B/
mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=jta-1.0.1B.jar

The issue was gone on performing the above two steps in an another Ubuntu 14.04 system.

It is really bad that everytime i have to do these two steps to make helium-karaf up and working.

Kindly suggest a solution

Thanks,
Chandralekha



 Comments   
Comment by George Boda [ 30/Oct/14 ]

I successfully ran the same set of commands on:

-Windows 7
-Java 1.8
-distribution-karaf-0.2.0-Helium.zip

###################################################
C:\Users\xyz>java -version
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) Client VM (build 25.25-b02, mixed mode, sharing)

####################################################

Karaf console output:

opendaylight-user@root>feature:install odl-ovsdb-openstack odl-ovsdb-northbound odl-restconf odl-mdsal-apidocs odl-adsal-all odl-adsal-northbound odl-dlux-core
Refreshing bundles org.apache.aries.util (13)
GossipRouter started at Thu Oct 30 10:19:09 GMT 2014
Listening on port 12001 bound on address 0.0.0.0/0.0.0.0
Backlog is 1000, linger timeout is 2000, and read timeout is 0
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://126.fwk2063372814:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://126.fwk2063372814:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://126.fwk2063372814:3/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]
Refreshing bundles org.ops4j.pax.web.pax-web-runtime (112), org.ops4j.pax.web.pax-web-jetty (113), com.sun.jersey.servlet (176)
opendaylight-user@root>
##################################################

Regs,

George

Comment by Thomas Bachman [ 05/Nov/14 ]

I think the critical piece of information here is that the environment that was used had never had an ODL build on it before. Once an ODL build had been performed, things worked. Maybe it's possible that it's pulling something from a local .m2?

Comment by Sharad Mishra [ 12/Nov/14 ]

I am still seeing this error with latest helium nightly snapshot builds (#35 dated Nov 12).

Comment by Sharad Mishra [ 14/Nov/14 ]

I built controller from source on this machine and still see the same error. Do I need to build something else - ovsdb, plugin ?

Comment by chandralekha [ 17/Nov/14 ]

Sharad Mishra,

I fixed the same issue in two of my fresh Ubuntu 14.04 following the same workaround. Was the compilation of source code is successful?

Comment by chandralekha [ 17/Nov/14 ]

(In reply to Sharad Mishra from comment #4)
> I built controller from source on this machine and still see the same error.
> Do I need to build something else - ovsdb, plugin ?

No we dont have to install ovsdb. The problem is when we run a pre-built package. It comes up with all the necessary maven projects. If any of the mavan project is missing locally in the system then we come across this issue. If you compiled the source code successfully which means all essential maven projects are built in your local system.

Comment by Sharad Mishra [ 03/Dec/14 ]

Rootcause of this issue is that karaf does not have access to network. Most likely it is caused by incorrect proxy settings. fixing proxy should resolve this issue.

Chandralekha, can you please confirm ?

Comment by chandralekha [ 23/Jan/15 ]

(In reply to Sharad Mishra from comment #7)
> Rootcause of this issue is that karaf does not have access to network. Most
> likely it is caused by incorrect proxy settings. fixing proxy should resolve
> this issue.
>
> Chandralekha, can you please confirm ?

Problem is still the same even when there is proper proxy settings

Comment by chandralekha [ 25/Feb/15 ]

Second Workaround:
If the mentioned workaround didn't help. This workaround will surely crack the problem.

Download the opendaylight integration source code as directed in wiki page and perform "mvn clean install"

Comment by Luis Gomez [ 19/Jun/15 ]

This has been finally fixed. Retry with Lithium Release.

Generated at Wed Feb 07 19:54:19 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.