[CONTROLLER-71] NETCONF does not apply previously stored configuration after controller restart Created: 30/Nov/13  Updated: 25/Jul/23  Resolved: 09/Jan/14

Status: Resolved
Project: controller
Component/s: config
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jan Medved Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: Macintosh

Attachments: Text File opendaylight.log    
External issue ID: 182
Priority: High

 Description   

After restarting the controller twice, a RESTCONF request to get inventory nodes hangs

 Comments   
Comment by Jan Medved [ 30/Nov/13 ]

Attachment opendaylight.log has been added with description: log file

Comment by Jan Medved [ 30/Nov/13 ]

Configured the controller as a server to which the netconf client should connect. Netconf connected and the controller node could be seen in inventory.

After controller restart, the committed netconf configuration was not applied, however, and inventory was empty.

Comment by Jan Medved [ 30/Nov/13 ]

This turned out to be a network connectivity problem.

(In reply to Jan Medved from comment #0)
> Created attachment 26 [details]
> log file
>
> After restarting the controller twice, a RESTCONF request to get inventory
> nodes hangs

Comment by Tony Tkacik [ 30/Nov/13 ]

From logs it seems configuration was not persisted -

  • possible reasons - long transaction
  • multiple Netconf clients connected at same time
Comment by Tomas Olvecky [ 09/Jan/14 ]

according to Tony this is fixed

Generated at Wed Feb 07 19:52:06 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.