config-resilience: Handle 'locate' failures in service-monitor
Bug #1480402 reported by
Hampapur Ajay
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Undecided
|
Rudra Rugge | |||
Trunk |
Fix Committed
|
Undecided
|
Rudra Rugge |
Bug Description
Encountered a case where there were inconsistent index <-> objects in config db (i.e. fq-name-to-id said object was present but in fact object was not present).
In this case service monitor failed in locate of this object (could be VMI/VN/SI) and service would forever be unavailable.
It would be preferable to restrict loss of svc-monitor service only to the failed project/VN.
tags: | added: config |
Changed in juniperopenstack: | |
assignee: | nobody → Rudra Rugge (rudrarugge) |
assignee: | Rudra Rugge (rudrarugge) → nobody |
assignee: | nobody → Prakash Bailkeri (prakashmb) |
Changed in juniperopenstack: | |
assignee: | Prakash Bailkeri (prakashmb) → Rudra Rugge (rudrarugge) |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/12859
Submitter: Rudra Rugge (<email address hidden>)