-
Bug
-
Resolution: Done
-
Highest
-
Oxygen
Both of these activators have a dependency on netconf-util activating and exposing NetconfConfiguration, but this is not expressed in any way OSGi would understand and order the startup. This leads to sporadic failures to activate because netconf-util is scheduled to activate after netconf-ssh or netconf-tcp.
This is evidenced here:
The simplest thing to do is to rewrite both netconf-ssh and netconf-tcp to use blueprint, so that the BP container starts only after netconf-util activates (i.e. NetconfConfiguration is published). Alternative is for the two activators to use a ServiceTracker – but that may prove too complex. In any case org.opendaylight.netconf.util.osgi.NetconfConfigUtil should be eliminated in the process.
- is duplicated by
-
NETCONF-518 SFT failure in netconf/features/netconf-connector/odl-netconf-topology/
- Resolved