[NETCONF-729] Steps to reproduce.rtf
karaf.log.1
network-instance.zip
[NETCONF-729] Sub-modules are not resolved during the formation of schema context Created: 30/Sep/20 Updated: 03/Jan/22 |
|
| Status: | Open |
| Project: | netconf |
| Component/s: | netconf, restconf-nb |
| Affects Version/s: | Magnesium, Aluminium, Sodium SR4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | vignesh karunakaran | Assignee: | Jamo Luhrsen |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ODL-sodium. Tried in ODL Magnesium and Aluminium(same error persists),Linux - Ubuntu. Java 11. NOKIA vSIM (SR OS 20.7) as a NETCONF device |
||
| Attachments: |
[NETCONF-729] Steps to reproduce.rtf
karaf.log.1
network-instance.zip
|
| Description |
|
I'm trying to connect the NOKIA-vSIM to the opendaylight contoller. The device is mounted successfully but after the capabilities are exchanged the ODL doesn't resolve the sub-modules included in the parent module. For example, openconfig-network-instance capability is unavailable since openconfig-network-instance-l2 is not resolved.... ... <schema> ... 2020-09-29T09:49:22,432 | WARN | remote-connector-processing-executor-10 | NetconfStateSchemas | 410 - org.opendaylight.netconf.sal-netconf-connector - 1.10.4 | - | RemoteDevice{vikee}: Ignoring schema due to missing namespace ... 2020-09-30T11:12:45,990 | WARN | remote-connector-processing-executor-11 | NetconfDevice | 293 - org.opendaylight.netconf.sal-netconf-connector - 1.12.0 | RemoteDevice{vsim1}: Unable to build schema context, unsatisfied imports {RevisionSourceIdentifier [name=openconfig-ospfv2@2017-02-28]=[ModuleImportImpl [name=openconfig-ospfv2-area, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-ospfv2-common, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-ospfv2-global, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-ospfv2-area-interface, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-ospfv2-lsdb, revision=null, semanticVersion=null]], RevisionSourceIdentifier [name=openconfig-mpls@2017-03-22]=[ModuleImportImpl [name=openconfig-mpls-static, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-mpls-igp, revision=null, semanticVersion=null]], RevisionSourceIdentifier [name=nokia-li-state@2020-04-21]=[ModuleImportImpl [name=nokia-state, revision=null, semanticVersion=null]], RevisionSourceIdentifier [name=openconfig-policy-forwarding@2016-11-08]=[ModuleImportImpl [name=openconfig-pf-interfaces, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-pf-path-groups, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-pf-forwarding-policies, revision=null, semanticVersion=null]], RevisionSourceIdentifier [name=openconfig-network-instance@2017-02-28]=[ModuleImportImpl [name=openconfig-network-instance-l2, revision=null, semanticVersion=null]], RevisionSourceIdentifier [name=openconfig-aaa@2018-04-12]=[ModuleImportImpl [name=openconfig-aaa-tacacs, revision=null, semanticVersion=null], ModuleImportImpl [name=openconfig-aaa-radius, revision=null, semanticVersion=null]]}, will reattempt with resolved only |
| Comments |
| Comment by Ivan Martiniak [ 16/Dec/21 ] |
|
Hello vignesh.karunakaran, Our support includes Silicon and Phosphorus, where I have tested affected submodules in yang validator and formation of schema context has been successful. Can you please let me know if issue is still present? |