Dear SFCiancs (SFCiados? SFCetians?), As part of working on a significant improvement to the odlparent SingleFeatureTest, so that it not only does a basic feature installation sanity check, but actually ensures that all bundles with their respective blueprint wiring really did all fully come up correctly (which is the big missing piece for some more sanity IMHO), see https://git.opendaylight.org/gerrit/#/c/48901/, we're seeing:
bundleState = Failure, due to: Blueprint. Unable to find property descriptor dataProvider on class org.opendaylight.sfc.sfc_netconf.provider.api.SfcNetconfServiceFunctionAPI. org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to find property descriptor dataProvider on class org.opendaylight.sfc.sfc_netconf.provider.api.SfcNetconfServiceFunctionAPI based on my analysis, I do not think that this is an infra issues in the new TestBundleDiag from c/48901, but suspect that your org.opendaylight.sfc.netconf bundle actually really does have broken BP wiring - is that possible, or am I totally off here? Indeed SfcNetconfServiceFunctionAPI's setDataProvider() method is static, so I don't think you can do <property name="dataProvider" ref="dataBroker"/> for <bean id="sfcnetconfservicefunctionapi" class="org.opendaylight.sfc.sfc_netconf.provider.api.SfcNetconfServiceFunctionAPI"> as you are in your sfc-netconf.xml ... at the very least, you would need a fake non-static setter there, like you have for setSfcProviderSfDescriptionMonitorAPI (although that's very ugly, static-is-evil; but that's beyond this thread). In order to unblock c/48901 (which is currently failing integration/distribution due to this), would one of you be able to resolve this in the sort of near term kind of future? Thanks a lot, M. -- Michael Vorburger <[email protected]> | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
