https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-386 netconf <p>Mounting fails with 2017-03-27 12:20:41,306 | DEBUG | lt-dispatcher-68 | AbstractSchemaRepository | 81 - org.opendaylight.yangtools.yang-model-util - 1.1.0.SNAPSHOT | Failed to acquire source from AbstractObjectRegistration</p> {instance=org.opendaylight.yangtools.yang.model.repo.spi.PotentialSchemaSource@5be51eb6} <p>akka.pattern.AskTimeoutException: Ask timed out on [Actor<span class="error">&#91;akka.tcp://opendaylight-cluster-data@192.168.10.20:2550/user/akka.tcp:opendaylight-cluster-data@192.168.10.20:2550_overcloud-controller-0.opnfv.org#-823207737&#93;</span>] after <span class="error">&#91;20000 ms&#93;</span>. Sender<span class="error">&#91;null&#93;</span> sent message of type "org.opendaylight.netconf.topology.singleton.messages.YangTextSchemaSourceRequest".<br/> at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:60</p> <p>and</p> <p>2017-03-27 12:20:41,306 | ERROR | lt-dispatcher-72 | Futures$CombinedFuture | 65 - com.google.guava - 18.0.0 | input future failed.<br/> org.opendaylight.yangtools.yang.model.repo.api.MissingSchemaSourceException: All available providers exhausted</p> <p>Operating System: Linux<br/> Platform: PC</p> NETCONF-386

Cannot mount honeycomb in clustered odl on CentOS

Bug Resolved Done Jakub Morvay Juraj Linkeš Mon, 27 Mar 2017 14:00:37 +0000 Fri, 15 Mar 2019 22:22:39 +0000 Fri, 7 Apr 2017 12:30:19 +0000 netconf 0 4 <p>Attachment overcloud-controller-0-karaf-try4.zip has been added with description: logs fron controller-0</p> <p>Attachment overcloud-controller-1-karaf-try4.zip has been added with description: logs fron controller-1</p> <p>Attachment overcloud-controller-2-karaf-try4.zip has been added with description: logs fron controller-2</p> <p>Attachment overcloud-controller-0-karaf-more-logs.log has been added with description: Logs from controller-0 after adding more logging into code</p> <p>Attachment overcloud-controller-1-karaf-more-logs.zip has been added with description: Logs from controller-1 after adding more logging into code</p> <p>Attachment overcloud-controller-2-karaf-more-logs.zip has been added with description: Logs from controller-2 after adding more logging into code</p> <p>It seems, that the actual problem we are hitting here is that custom schema-cache-directory is not working correctly in clustered setting.</p> <p>Mounting a netconf device in clustered setting goes as follows. Leader for netconf mounpoint is elected (this is done with help of clustering singleton service), leader mounts a device and notifies followers about mounting result. Part of the leader's mount process is device schema resolution. </p> <p>Leader downloads all the schema sources from device, registers them with its schema registry and schema repository and finally builds schema context. After that, leader sends followers list of supported source ids and also creates actor that serves the sources upon followers' requests. It seems, that this actor is injected with wrong schema repository so it cannot serve followers requests and we see this failures in the log.</p> <p>The bug should be present in a setting where we specify a custom schema-cache-directory for a netconf mount. Default setting shouldn't cause any problems.</p> <p>When using this configuration:<br/> {<br/> "topology": [<br/> {<br/> "node": [</p> { "netconf-node-topology:actor-response-wait-time": 20, "netconf-node-topology:between-attempts-timeout-millis": 10000, "netconf-node-topology:connection-timeout-millis": 10000, "netconf-node-topology:default-request-timeout-millis": 10000, "netconf-node-topology:host": "192.168.10.25", "netconf-node-topology:keepalive-delay": 0, "netconf-node-topology:max-connection-attempts": 10, "netconf-node-topology:password": "admin", "netconf-node-topology:port": 2831, "netconf-node-topology:tcp-only": false, "netconf-node-topology:username": "admin", "node-id": "overcloud-controller-0.opnfv.org" } <p> ],<br/> "topology-id": "topology-netconf"<br/> }<br/> ]<br/> }</p> <p>the errors disappeared. The errors were present only when I used a custom schema-cache-directory, e.g. "netconf-node-topology:schema-cache-directory": "hcmount"</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/54017/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/54017/</a></p> <p>A suite attempting to detect this Bug has been merged <span class="error">&#91;0&#93;</span>.<br/> But I was unable to find a build where the suite fails.</p> <p>The suite uses netconf-testtool and manipulates device data modeled by car.yang which is both exported by testtool and present in ODL-local /tmp/schema directory (on every cluster member).</p> <p>Please, let me know if you find a build which fails on the suite, or if you spot a difference between the scenario the suite is testing and original Bug description.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://git.opendaylight.org/gerrit/54110" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/54110</a></p> Development External issue ID 8086 External issue URL Rank 0|i01y7z: