[GENIUS-206] Stale entries in AlivenessMonitor Datastore Created: 24/Aug/18 Updated: 15/Feb/19 Resolved: 15/Feb/19 |
|
| Status: | Verified |
| Project: | genius |
| Component/s: | None |
| Affects Version/s: | Oxygen-SR4, Fluorine-SR1, Neon |
| Fix Version/s: | Fluorine-SR2, Neon |
| Type: | Bug | Priority: | Low |
| Reporter: | Nobin Mathew | Assignee: | Nobin Mathew |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
I see that following DS remain stale even after MIP is removed successfully. Other aliveness monitor data stores are cleaned properly except following ones :
http://localhost:8181/restconf/operational/aliveness-monitor:monitorid-key-map/
{ "monitorid-key-map": { "monitorid-key-entry": [ { "monitor-id": 2, "monitor-key": "5e0fc8db-66d5-4a2c-969c-407b97bd4422.10.1.1.1.10.1.1.110.Arp" } ] } }
http://localhost:8181/restconf/operational/aliveness-monitor:interface-monitor-map/
{ "interface-monitor-map": { "interface-monitor-entry": [ { "interface-name": "5e0fc8db-66d5-4a2c-969c-407b97bd4422" } ] } } |
| Comments |
| Comment by Faseela K [ 01/Sep/18 ] |
|
Let us cherry-pick to stable/oxygen as well, and close the Jira once the fluorine and oxygen patches are merged |