Hi Ivan and Everybody,

I pushed the code and it failed at the PacketHandler test:
https://jenkins.opendaylight.org/releng/job/l2switch-maven-verify-master-mvn38-openjdk11/3/

The logs for this failure are here:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/l2switch-maven-verify-master-mvn38-openjdk11/3

The first error at file *console.log* says the following:
[ERROR] 
installFeatureCatchAndLog(org.opendaylight.odlparent.featuretest.SingleFeatureTest)[repoUrl:
 
file:/w/workspace/l2switch-maven-verify-master-mvn38-openjdk11/features/odl-l2switch-packethandler/target/feature/feature.xml,
 Feature: odl-l2switch-packethandler 0.8.0.SNAPSHOT]  Time elapsed: 24.21 s  
<<< ERROR!
org.opendaylight.odlparent.bundlestest.lib.SystemStateFailureException: 
diag failed; some bundles failed to start
diag: Failure {Installed=0, Resolved=7, Unknown=0, GracePeriod=4, Waiting=1, 
Starting=0, Active=318, Stopping=0, Failure=1}

And it seems that the problem is in *yang* 
(org.opendaylight.yang.gen.v1.urn.opendaylight.serviceutils.srm.rpc.rev180626.OdlSrmRpcsService).
 The error states the following:
Error getting RPC service for 
org.opendaylight.yang.gen.v1.urn.opendaylight.serviceutils.srm.rpc.rev180626.OdlSrmRpcsService
org.osgi.service.blueprint.container.ComponentDefinitionException: Error 
getting RPC service for 
org.opendaylight.yang.gen.v1.urn.opendaylight.serviceutils.srm.rpc.rev180626.OdlSrmRpcsService
        at 
org.opendaylight.controller.blueprint.ext.AbstractInvokableServiceMetadata.create(AbstractInvokableServiceMetadata.java:141)
        at 
org.apache.aries.blueprint.di.ComponentFactoryRecipe.internalCreate(ComponentFactoryRecipe.java:47)
        at 
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:108)
        at 
org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360)
        at 
org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:190)
        at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:737)
        at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:433)
        at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
org.apache.aries.blueprint.container.ExecutorServiceWrapper.run(ExecutorServiceWrapper.java:106)
        at 
org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.google.common.base.VerifyException: expected a non-null reference
        at com.google.common.base.Verify.verify(Verify.java:124)
        at com.google.common.base.Verify.verifyNotNull(Verify.java:500)
        at com.google.common.base.Verify.verifyNotNull(Verify.java:477)
        at 
org.opendaylight.mdsal.binding.dom.adapter.osgi.AbstractAdaptedService.delegate(AbstractAdaptedService.java:44)
        at 
org.opendaylight.mdsal.binding.dom.adapter.osgi.OSGiRpcConsumerRegistry.getRpcService(OSGiRpcConsumerRegistry.java:31)
        at 
org.opendaylight.controller.blueprint.ext.AbstractInvokableServiceMetadata.create(AbstractInvokableServiceMetadata.java:135)
        ... 17 more

The only idea I have to solve this problem is changing the mdsal to yang 
binding version at file packethandler/model/pom.xml from 6.0.0 to 6.0.10.

Should I try this or is there a more obvious solution I have not seen?

Regards,

David


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9019): https://lists.opendaylight.org/g/Discuss/message/9019
Mute This Topic: https://lists.opendaylight.org/mt/99883508/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to