Soma created KARAF-7945:
---------------------------
Summary: Unable to start blueprint container XXX due to unresolved
dependencies
Key: KARAF-7945
URL: https://issues.apache.org/jira/browse/KARAF-7945
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.1.5
Reporter: Soma
We are running an Opendaylight where it uses the karaf 4.1.5.
After the Karaf start And all bundle load timeout, We see the bundle:diag is
fine.
But
The Servlet related to the diagstatus and restconf are not up because the
bundle load issue.
While loading the bundles we are getting the logs
2025-02-12T07:48:36,989 | ERROR | Blueprint Extender: 2 |
BlueprintContainerImpl | Unable to start blueprint container for
bundle org.opendaylight.netconf.restconf-nb-bierman02/1.7.4.SNAPSHOT due to
unresolved dependencies [(objectClass=org.opendaylight.aaa.api.AAAService)]
2025-02-12T07:48:44,049 | ERROR | Blueprint Extender: 2 |
BlueprintContainerImpl | Unable to start blueprint container for
bundle org.opendaylight.neutron.northbound-api/0.10.4.SNAPSHOT due to
unresolved dependencies
[(objectClass=org.opendaylight.netconf.sal.restconf.api.JSONRestconfService)]
2025-02-12T07:48:44,616 | ERROR | Blueprint Extender: 2 |
BlueprintContainerImpl | Unable to start blueprint container for
bundle org.opendaylight.aaa.aaa-shiro/0.7.4.SNAPSHOT due to unresolved
dependencies
[(&(|(type=default)(!(type=*)))(objectClass=org.osgi.service.http.HttpService))]
We have a timeout of 11 Min for all the bundle load. within this time the
bundle restart is done twice But the Some services are not up.
in the *scr:info org.ops4j.pax.web.service.internal.WhiteboardDtoService*
The servlet related to the bundles
300 | Active | 80 | 1.3.4.SNAPSHOT | diagstatus-web
265 | Active | 80 | 6.0.4.SNAPSHOT | ODL :: sdnc ::
counteraggregator
359 | Active | 80 | 1.7.4.SNAPSHOT | MD SAL Restconf
Connector
395 | Active | 80 | 0.10.4.SNAPSHOT |
org.opendaylight.neutron.northbound-api
are not loaded in the system.
Because of this curl hit to the API are failing with the HTTP erro 404.
What is the cause of this issue,.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
