[NETCONF-225] Connection to config subsystem netconf endpoint refused Created: 04/Jul/16 Updated: 15/Mar/19 Resolved: 18/Jul/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Peter Gubka | Assignee: | Jakub Morvay |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6154 |
| Description |
|
in builds #19 and #20 it is done well used feature: odl-netconf-clustered-topology this job tries configure netconf device via restconf firstly and then using this device to configure bgp peer after PUT restconf/config/network-topology:network-topology/topology/topology-netconf/node/peer-controller-config Now the problem is that GET restconf/config/network-topology:network-topology/topology/topology-netconf/node/peer-controller-config/yang-ext:mount This happened also in the past. The reason was the within some akka timeout some processes or dependencies were not completed. As a workaround the test suite tried 3 times to configure that device in the following loop The problem now is that even that workaround stopped working. |
| Comments |
| Comment by Jakub Morvay [ 14/Jul/16 ] |
|
Actually, this is not related to netconf clustering. Config subsystem SSH server listens on address 127.0.0.1 and thus is reachable only on localhost and on this adsress. Here is patch that makes SSH server listen on adress 0.0.0.0, so it will listen on |