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.
Added exception handling to log and skip the missing objects.
Reviewed: https:/ /review. opencontrail. org/12859 github. org/Juniper/ contrail- controller/ commit/ ca2565b516e17f9 6e31ce74bf86b58 d86a8d6e73
Committed: http://
Submitter: Zuul
Branch: master
commit ca2565b516e17f9 6e31ce74bf86b58 d86a8d6e73
Author: Rudra Rugge <email address hidden>
Date: Sat Jul 25 11:54:24 2015 -0700
Handle 'locate' failures in service-monitor
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.
Added exception handling to log and skip the missing objects.
Change-Id: Idd3400742f2c3e 207d4c149a17852 4780fa0b003
Closes-Bug: #1480402