Ask Your Question
0

What is the meaning, cause and steps to resolve org.opendaylight.yangtools.yang.model.repo.api.MissingSchemaSourceException: No providers registered for sourceSourceIdentifier?

asked 2015-10-05 06:16:15 -0700

baxteran gravatar image

Hello ODL community,

I'm trying to register a Junos device, a Juniper MX running Junos 15.1 with the ODL netconf adapter.

Environment:

  • Lithium-SR1 on Ubuntu 14.04 LTS
  • All netconf features enabled in karaf

Setup:

I've followed the tutorial at https://wiki.opendaylight.org/view/OpenDaylightController:Config:Examples:Netconf#Usingnetopeernetconfserverinsteadofa real_device - this yields successful results. I know that my target device does not support netconf monitoring - therefore I have: 1. sideloaded the yang schemas for the Juniper device into the odl cache/schema directory 2. written a script to register my device with the adapter. 3. verified that the expected config has been applied by checking http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules/module/odl-sal-netconf-connector-cfg:sal-netconf-connector/junos-testmx-netconf-device 4. Verified that my target device is reachable by invoking 'ssh userrname@ipaddress -p 830 -s netconf' and verifiying sensible output.

But the first smell that something is not right comes from my yang models not being listed in YangUI

Digging further I find the following messages in the karaf log:

2015-10-05 10:58:18,922 | INFO | NioProcessor-5 | ClientSessionImpl | 142 - org.apache.sshd.core - 0.14.0 | Dequeing pending packets 2015-10-05 10:58:19,252 | INFO | NioProcessor-5 | ClientUserAuthServiceNew | 142 - org.apache.sshd.core - 0.14.0 | Received SSHMSGUSERAUTHFAILURE 2015-10-05 10:58:19,336 | INFO | NioProcessor-5 | UserAuthKeyboardInteractive | 142 - org.apache.sshd.core - 0.14.0 | Received
2015-10-05 10:58:19,444 | INFO | NioProcessor-5 | UserAuthKeyboardInteractive | 142 - org.apache.sshd.core - 0.14.0 | Received
2015-10-05 10:58:19,522 | INFO | NioProcessor-5 | ClientUserAuthServiceNew | 142 - org.apache.sshd.core - 0.14.0 | Received SSH
MSGUSERAUTHSUCCESS 2015-10-05 10:58:20,361 | WARN | sing-executor-13 | NetconfStateSchemas | 184 - org.opendaylight.controller.sal-netconf-connector - 1.2.1.Lithium-SR1 | {}: Netconf monitoring not supported on device, cannot detect provided schemas 2015-10-05 10:58:20,368 | WARN | sing-executor-13 | NetconfDevice | 184 - org.opendaylight.controller.sal-netconf-connector - 1.2.1.Lithium-SR1 | RemoteDevice{junos-testmx-netconf-device}: Netconf device does not provide all yang models reported in hello message capabilities, required but not provided: [(urn:ietf:params:xml:ns:yang:junos-extension-15.1?revision=2015-05-29)junos-extension, (urn:ietf:params:xml:ns:yang:configuration-15.1?revision=2015-05-29)configuration] 2015-10-05 10:58:20,368 | WARN | sing-executor-13 | NetconfDevice | 184 - org.opendaylight.controller.sal-netconf-connector - 1.2.1.Lithium-SR1 | RemoteDevice{junos-testmx-netconf-device}: Attempting to build schema context from required sources 2015-10-05 10:58:20,384 | ERROR | sing-executor-14 | Futures$CombinedFuture | 64 - com.google.guava - 18.0.0 | input future failed. org.opendaylight.yangtools.yang.model.repo.api.MissingSchemaSourceException: No providers registered for sourceSourceIdentifier [name=configuration@2015-05-29] at org.opendaylight.yangtools.yang.model.repo.util.AbstractSchemaRepository.getSchemaSource(AbstractSchemaRepository.java:92)[92:org.opendaylight.yangtools.yang-model-util:0.7.1.Lithium-SR1] at org.opendaylight.yangtools.yang.parser.repo.SharedSchemaContextFactory$1.apply(SharedSchemaContextFactory.java:66)[94:org.opendaylight.yangtools.yang-parser-impl:0.7.1.Lithium-SR1] at org.opendaylight.yangtools.yang.parser.repo.SharedSchemaContextFactory$1.apply(SharedSchemaContextFactory.java:63)[94:org.opendaylight.yangtools.yang-parser-impl:0.7.1.Lithium-SR1] at com.google.common.collect.Iterators ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-10-07 04:34:11 -0700

baxteran gravatar image

Hi,

solved this myself - the message means 'I can't find the yang schema for this device in my cache'

This is because the Juniper yang models include a version number in the filename which makes them non-identical to the module name. A quick experiment with filenames in the cache resolves.

Hope that helps someone.

Andy.

edit flag offensive delete publish link more

Comments

Can you please share how you side loaded the schema and the script you used to register the device?

sronan ( 2015-10-07 09:07:46 -0700 )edit

Please provide what filename actually worked. I realize this is an old thread, but it is not helpful to simply state that renaming files fixed the problem. I have this exact same problem and cannot figure out what to name the files.

berkheimert ( 2016-11-29 18:48:27 -0700 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Stats

Asked: 2015-10-05 06:16:15 -0700

Seen: 285 times

Last updated: Oct 07 '15