[CONTROLLER-1062] Clustering: Fail to clean up operational state after controller restart Created: 08/Dec/14  Updated: 19/Oct/17  Resolved: 02/Jun/15

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Helium
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: All
Platform: All

External issue ID: 2490

 Description   

When Controller with CDS and persistence is restarted, and no mininet is connected to the controller after the restart, nodes that used to be connected to the controller before the restart are still reported through RESTCONF.

to reproduce:

  • Enable clustering and persistence
  • Connect mininet
  • kill controller
  • exit mininet
  • Restart controller

 Comments   
Comment by Carol Sanders [ 02/Jun/15 ]

This is expected behavior if operational persistence is turned on. It is not turned on by default.

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