First reported here: https://lists.opendaylight.org/pipermail/controller-dev/2015-April/008945.html

There is a difference in the behavior of the config subsystem in normal karaf and in a karaf instance (a separate process created by karaf). It does not seem to register services as it should.

Problem verified in Helium-SR1 and Helium-SR3.

Minimal steps to reproduce in Helium-SR1:

./bin/karaf
instance:create test

run:
echo 'org.ops4j.pax.url.mvn.localRepository=${karaf.home}/${karaf.default.repository}' >> ./instances/test/etc/org.ops4j.pax.url.mvn.cfg

instance:start test
instance:connect test
feature:repo-add mvn:org.opendaylight.integration/features-integration/0.2.1-Helium-SR1/xml/features

feature:install odl-config-netty

services | grep io.netty.util.Timer

Expected output:
[io.netty.util.Timer]

Actual output: None

The same feature can be installed in root context, and it would expose the service from netty-timer-config. In instance context, the service is not there, even though all the bundles are active.

Here are the bundle details on my machine:

– Instance context: –

opendaylight-user@test>bundle:capabilities 147
org.opendaylight.controller.netty-timer-config [147] provides:
--------------------------------------------------------------
// ... snipped ...
service; [org.opendaylight.controller.config.spi.ModuleFactory] with properties:
service.id = 634
Used by:
org.opendaylight.controller.config-manager [120]

– Root context: –

opendaylight-user@root>bundle:capabilities 147
org.opendaylight.controller.netty-timer-config_0.2.6.Helium-SR1 [147] provides:
-------------------------------------------------------------------------------
// ... snipped ...
service; [org.opendaylight.controller.config.spi.ModuleFactory] with properties:
service.id = 657
Used by:
org.opendaylight.controller.config-manager_0.2.6.Helium-SR1 [120]
service; [io.netty.util.Timer] with properties:
name = global-timer
service.id = 664