Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

[INFO] Failed to fully assemble schema context for [...]

Description

when running SingleFeatureTest (SFT) on a Karaf 4 feature, e.g. by "mvn -o -Dsft.diag.skip=true clean install" in genius/features/features4-genius from https://git.opendaylight.org/gerrit/#/c/51966/,

but I think completely unrelated to that change, and this happens even on Karaf 3 not just 4 and also in production instances, there are typically a lot of "scary looking" (because they have a stack trace..) INFO messages like the one below in the log.

I'm not aware of any actual issues - just sayin' that this looks quite confusing, e.g. when you scan logs for other errors.

looks like it may be vaguely related.. should the level of this particular log perhaps be reduced from INFO to DEBUG? Or should it at least not log it's stack trace?

Activity

Show:

Robert Varga February 28, 2020 at 1:37 PM

Resolved by adding a Karaf-specific wrapper around YangModuleInfoRegistry, which is bypassed if FeaturesService is not available.

Robert Varga May 2, 2017 at 12:21 AM

Karaf 4.1.2 and 4.2.0 will have FeatureService.registerListener(DeploymentListener), which gives events on start, resolve and end of deployment.

Robert Varga April 27, 2017 at 6:13 PM

This new implementation should then be packaged into the feature in place of the osgi scanner, hence our karaf deployments will not see the log entries mentioned.

Robert Varga April 27, 2017 at 6:11 PM

Once is addressed, we need to create mdsal-dom-schema-service-karaf, which will talk to Karaf's FeatureService and do bundle scan throttling based on the events from it.

Robert Varga April 26, 2017 at 7:27 PM

Done

Details

Assignee

Reporter

Components

Fix versions

Priority

Created March 8, 2017 at 1:54 AM
Updated February 28, 2020 at 2:58 PM
Resolved February 28, 2020 at 2:58 PM