I've opened bug 8342 against the controller to try to figure it out:
https://bugs.opendaylight.org/show_bug.cgi?id=8342
--Colin
On Mon, May 1, 2017 at 4:37 PM, Tom Pantelis wrote:
> The ClassLoadingStrategy service is advertised by the ConfigManagerActivator
> (a bundle activator). I don't see
The ClassLoadingStrategy service is advertised by the ConfigManagerActivator
(a bundle activator). I don't see any errors logged for it. Maybe that
bundle didn't start for some reason? Or maybe the
mdsal-binding-generator-api bundle that exports the ClassLoadingStrategy
class re-installed/restarte
That seems to be the root of the issues with our SFT hangs. Between SFT
hangs and the BGP test that hangs, those account for 12 of the last 16
failures in autorelease that we don't have fixes for.
--Colin
On Mon, May 1, 2017 at 4:12 PM, Tom Pantelis wrote:
> yeah - saw that too:
>
> 2017-05-01
yeah - saw that too:
2017-05-01 10:44:13,976 | ERROR | rint Extender: 1 |
BlueprintContainerImpl | 12 -
org.apache.aries.blueprint.core - 1.7.1 | Unable to start blueprint
container for bundle
org.opendaylight.controller.sal-binding-broker-impl/1.5.0.Carbon due
to unresolved dependencies
It seems like there's something wrong with who sal-binding-broker-impl
comes up and doesn't get the ClassLoadingStrategy and then SFT hangs. So
far, thats' the first exception that happens in every SFT hang I've looked
into.
Robert, TomP, any ideas what would cause this. It looks like the AAA issu
