[INTDIST-68] distribution-check is not stable in Nitrogen Created: 26/Apr/17 Updated: 21/Mar/18 Resolved: 21/Mar/18 |
|
| Status: | Resolved |
| Project: | integration-distribution |
| Component/s: | Build |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Luis Gomez | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 8304 | ||||||||
| Description |
|
We see these kind of failures in karaf 4 SFT: 6:35:16 ------------------------------------------------------- 16:36:03 1. NOK org.opendaylight.aaa.cert: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint 16:36:03 4/25/17 4:35 PM 16:36:03 Missing dependencies: 16:36:03 (objectClass=org.opendaylight.aaa.encrypt.AAAEncryptionService) 16:36:03 16:36:03 2. NOK org.opendaylight.aaa.encrypt-service: OSGi state = Active, Karaf bundleState = Stopping 16:36:03 3. NOK org.opendaylight.aaa.shiro: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint 16:36:03 4/25/17 4:35 PM 16:36:03 Missing dependencies: 16:36:03 (objectClass=org.opendaylight.aaa.cert.api.ICertificateManager) 16:36:03 16:36:03 4. NOK org.opendaylight.lispflowmapping.mappingservice.implementation: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint 16:36:03 4/25/17 4:35 PM 16:36:03 Missing dependencies: 16:36:03 Available DOM RPC for binding RPC: interface org.opendaylight.yang.gen.v1.urn.opendaylight.lfm.lisp.sb.rev150904.OdlLispSbService 16:36:03 16:36:03 5. NOK org.opendaylight.lispflowmapping.mappingservice.southbound: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint 16:36:03 4/25/17 4:35 PM 16:36:03 Missing dependencies: 16:36:03 (objectClass=org.opendaylight.controller.md.sal.binding.api.NotificationPublishService) 16:36:03 16:36:03 at org.opendaylight.odlparent.bundles4test.TestBundleDiag.checkBundleDiagInfos(TestBundleDiag.java:86) 16:36:03 at org.opendaylight.odlparent.bundles4test.TestBundleDiag.checkBundleDiagInfos(TestBundleDiag.java:50) 16:36:03 at org.opendaylight.odlparent.featuretest.SingleFeatureTest.installFeature(SingleFeatureTest.java:387) 16:36:03 at org.opendaylight.odlparent.featuretest.SingleFeatureTest.installFeatureCatchAndLog(SingleFeatureTest.java:338) 16:36:03 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 16:36:03 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 16:36:03 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 16:36:03 at java.lang.reflect.Method.invoke(Method.java:498) 16:36:03 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) 16:36:03 at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) 16:36:03 at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) 16:36:03 at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) 16:36:03 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) 16:36:03 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) 16:36:03 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 16:36:03 at java.lang.Thread.run(Thread.java:745) 16:36:03 16:36:03 16:36:03 Results : 16:36:03 16:36:03 Failed tests: 16:36:03 diag: Stopping {Starting=0, Unknown=0, Stopping=1, Waiting=0, Active=326, Resolved=4, GracePeriod=4, Failure=0, Installed=0} 16:36:03 1. NOK org.opendaylight.aaa.cert: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint |
| Comments |
| Comment by Luis Gomez [ 26/Apr/17 ] |
|
Not sure if int/dist is where this has to be fixed but I am opening this here until we have more clarity which project should be responsible. |
| Comment by Vratko Polak [ 26/Apr/17 ] |
|
Can anyone identify which merge has caused this? |
| Comment by Vratko Polak [ 26/Apr/17 ] |
|
> Can anyone identify which merge has caused this? I mean after Lispflowmapping passed [1], something (in an upstream ODL project) has to have changed. [1] https://jenkins.opendaylight.org/releng/job/distribution-check-nitrogen/18/ |
| Comment by Luis Gomez [ 26/Apr/17 ] |
|
I think there are 2 patches responsible for this: 1) The lisp patch I already removed. Problem is if we remove the second we cannot do distribution-check anymore, right? |
| Comment by Luis Gomez [ 26/Apr/17 ] |
|
Lets try this anyway: |
| Comment by Colin Dixon [ 26/Apr/17 ] |
|
I think this is related to or a duplicate of BUG-8313 |
| Comment by Vratko Polak [ 26/Apr/17 ] |
|
> 55255 Yes. Possibly this happened because aaa merge job [4] was late to pass, and in the meantime Lispflowmapping pulled in a feature which combined into this Bug. > BUG-8313 Yes, fixing that may fix this as well. [4] https://jenkins.opendaylight.org/releng/job/aaa-merge-nitrogen/9 |
| Comment by Luis Gomez [ 26/Apr/17 ] |
|
My patch did not work so we really have to wait for the aaa fix or temporary disable karaf 4 distribution-check. |
| Comment by Luis Gomez [ 21/Mar/18 ] |
|
This was fixed. |