[NETCONF-144] Documentation needed for device reconnect based on schema change Created: 09/Feb/16 Updated: 15/Mar/19 Resolved: 01/Oct/18 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Jakub Morvay |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5281 |
| Description |
|
When Beryllium is started (without additional features in featuresBoot), then feature:install odl-netconf-connector-all and then feature:install another feature (for example odl-bgpcep-bgp), this is seen in karaf.log: 2016-02-09 10:41:03,007 | INFO | oupCloseable-6-1 | NetconfDevice | 182 - org.opendaylight.netconf.sal-netconf-connector - 1.3.0.SNAPSHOT | RemoteDevice {controller-config}: Schemas change detected, reconnecting2016-02-09 10:41:03,011 | WARN | oupCloseable-6-1 | NetconfDeviceCommunicator | 182 - org.opendaylight.netconf.sal-netconf-connector - 1.3.0.SNAPSHOT | RemoteDevice{controller-config} : Session went down The connection seem to re-establish successfully, but there is a brief period when controller-config device fails on any operation. This behavior is relevant for csit tests, suites should retry the operation as in this specific case failure is not an error. There needs to be a wikipage explaining this behavior, so that test developers are informed. |
| Comments |
| Comment by Vratko Polak [ 10/Feb/16 ] |
|
> there is a brief period when controller-config device fails on any operation. I have seen jobs actually stuck on such operation, waiting for hours. |
| Comment by Jakub Morvay [ 01/Oct/18 ] |
|
config subsytem was removed completely, there is no point in creating loopback connection to CSS netconf server endpoint. This issue is no longer valid. |