[NETCONF-193] Netconf connectors unreadable due to "data model content does not exist" Created: 03/May/16 Updated: 15/Mar/19 Resolved: 02/Jun/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 5832 | ||||||||
| Description |
|
Observed on: Boron, "only", with suite "netconfready.robot" If content of any Netconf connectors (or the list of Netconf connectors) is requersted (URIs under "restconf/config/network-topology:network-topology/topology/topology-netconf"), the received response is always the following error: "Request could not be completed because the relevant data model content does not exist". What is strange is that creating or deleting Netconf connectors appears to work (received response code is of the 2xx variety). |
| Comments |
| Comment by Jozef Behran [ 03/May/16 ] |
|
After a better look at the test results it turns out that this is most likely a "ODL boot performance" problem. Namely, further down there is a CRUD suite which can access the netconf connectors just fine. |
| Comment by Jozef Behran [ 05/May/16 ] |
|
It turns out that this is not an "ODL performance problem". The CRUD suite after the failed Netconf readiness did not report any failed tests (which caused me to suspect that the ODL boot performance is to be blamed). So I tried to increased the netconf boot wait timeout to 15 minutes and it still fails. The conclusion is that this seems to be one of these "Netconf looks to be broken until first used" bugs that disappear on first use (in this case Netconf fixes itself after a device is configured and connected). |
| Comment by Vratko Polak [ 26/May/16 ] |
|
Is there any symptom of this bug not covered by |
| Comment by Jakub Morvay [ 02/Jun/16 ] |
|
Suite "netconfready.robot" should work fine now. Closing this bug as this is duplicate of |