When cumin is running and sesame gets restarted, the old instance
is deleted and another one created. But when I shut down cumin
first, then restart sesame, start cumin again, there the old
record stays forever and a new one appears as well.
I expect cumin to be able to remove old stale entries after some
time even if it does not get "agent delete" message first.
How reproducible: 100%
This happens for all agents that do not have a stable id. Recommendation here is that stable id is the agent's responsibility, not cumin's.
Still at issue is what to do when agents go away forever while cumin is not watching (down).
*** This bug has been marked as a duplicate of bug 623197 ***
See Bug 622522
The other part (old records staying in the list for long time)
was solved by Bug 595774.