[NETCONF-406] ietf-netconf-monitoring capability with deviation Created: 24/Apr/17 Updated: 15/Mar/19 Resolved: 28/Aug/18 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Dhirendra Kumar Trivedi | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8279 |
| Description |
|
We are supporting ietf-netconf-monitoring YANG model but partially, so now we need to advertise the deviation module but it seems OpenDaylight controller is not taking it as valid capability. Am i missing something here ? Logs: 2017-04-21 10:46:29,243 | DEBUG | upCloseable-3-21 | AbstractNetconfSession | 98 - org.opendaylight.netconf.netty-util - 1.1.1.Boron-SR1 | Session 73366 created 2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfClientSession | 261 - org.opendaylight.netconf.client - 1.1.1.Boron-SR1 | Client Session NetconfClientSession {sessionId=73366, channel=[id: 0xce8cf541]}created 2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfClientSessionNegotiator | 261 - org.opendaylight.netconf.client - 1.1.1.Boron-SR1 | Netconf session NetconfClientSession {sessionId=73366, channel=[id: 0xce8cf541]}isn't capable of using exi. 2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | AbstractNetconfSession | 98 - org.opendaylight.netconf.netty-util - 1.1.1.Boron-SR1 | SessionNetconfClientSession {sessionId=73366, channel=[id: 0xce8cf541]}up 2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfDeviceCommunicator | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice {bag3r_vmx}: Session established2017-04-21 10:46:29,244 | TRACE | upCloseable-3-21 | NetconfDeviceCommunicator | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice{bag3r_vmx} : Session advertised capabilities: NetconfSessionPreferences {capabilities=[http://xml.juniper.net/dmi/system/1.0, urn:ietf:params:netconf:capability:url:1.0?protocol=http,ftp,file, urn:ietf:params:xml:ns:netconf:capability:candidate:1.0, urn:ietf:params:netconf:capability:confirmed-commit:1.0, http://xml.juniper.net/netconf/junos/1.0, urn:ietf:params:xml:ns:netconf:capability:validate:1.0, urn:ietf:params:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file,urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0, urn:ietf:params:netconf:capability:validate:1.0, urn:ietf:params:netconf:capability:candidate:1.0], moduleBasedCapabilities=[(http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3)jnx-ietf-netconf-monitoring-dev, (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring)ietf-netconf-monitoring], rollback=false, monitoring=false, candidate=true, writableRunning=false}2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice {bag3r_vmx}: Session to remote device established with NetconfSessionPreferences{capabilities=[http://xml.juniper.net/dmi/system/1.0, urn:ietf:params:netconf:capability:url:1.0?protocol=http,ftp,file, urn:ietf:params:xml:ns:netconf:capability:candidate:1.0, urn:ietf:params:netconf:capability:confirmed-commit:1.0, http://xml.juniper.net/netconf/junos/1.0, urn:ietf:params:xml:ns:netconf:capability:validate:1.0, urn:ietf:params:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file, urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0, urn:ietf:params:netconf:capability:validate:1.0, urn:ietf:params:netconf:capability:candidate:1.0], moduleBasedCapabilities=[(http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3)jnx-ietf-netconf-monitoring-dev, (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring)ietf-netconf-monitoring], rollback=false, monitoring=false, candidate=true, writableRunning=false}2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | RemoteDeviceConnectorImpl | 267 - org.opendaylight.netconf.topology-singleton - 1.1.1.Boron-SR1 |RemoteDevice{bag3r_vmx} : Connector started successfully 2017-04-21 10:46:29,244 | DEBUG | ssing-executor-2 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice {bag3r_vmx}: Schemas exposed by ietf-netconf-monitoring: []2017-04-21 10:46:29,245 | WARN | ssing-executor-2 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice{bag3r_vmx} : Netconf device does not provide all yang models reported in hello message capabilities, required but not provided: [(http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3)jnx-ietf-netconf-monitoring-dev, (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring)ietf-netconf-monitoring] 2017-04-21 10:46:29,245 | WARN | ssing-executor-2 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice {bag3r_vmx}: Attempting to build schema context from required sources2017-04-21 10:46:29,246 | ERROR | ssing-executor-2 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice{bag3r_vmx} : Initialization in sal failed, disconnecting from devicejava.lang.IllegalStateException: RemoteDevice {bag3r_vmx}: No more sources for schema context at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.setUpSchema(NetconfDevice.java:479)[263:org.opendaylight.netconf.sal-netconf-connector:1.4.1.Boron-SR1] at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.run(NetconfDevice.java:428)[263:org.opendaylight.netconf.sal-netconf-connector:1.4.1.Boron-SR1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121] |
| Comments |
| Comment by Tomas Cere [ 24/Apr/17 ] |
|
Deviations were added to yangtools in carbon and are not yet supported on netconf side. |
| Comment by Robert Varga [ 24/Apr/17 ] |
|
Actually the problem seems to be that jnx-ietf-netconf-monitoring-dev is not advertized via netconf-monitoring and hence we do not have a source for that model – pre-populating it to the model cache may help. |
| Comment by Robert Varga [ 02/May/17 ] |
|
Has providing the module helped? If not, can you provide karaf.log files from the failed connection attempt. |
| Comment by Robert Varga [ 28/Aug/18 ] |
|
15+ months without a response, closing this issue. |