config_api_svcmonitor_1 container continuously restarting in all the Contrail controllers

config_api_svcmonitor_1 container continuously restarting in all the Contrail controllers

The shown error messages are seen in contrail logs which indicates some loadbalancer objects are not having 'vip_subnet_id'. config_svcmonitor_1 is restarting because some LB object is not having vip_subnet_id details.

 File "/usr/lib/python2.7/site-packages/svc_monitor/loadbalancer_agent.py", line 299, in loadbalancer_add

   lb = self.loadbalancer_get_reqdict(loadbalancer)

 File "/usr/lib/python2.7/site-packages/svc_monitor/loadbalancer_agent.py", line 509, in loadbalancer_get_reqdict

   'subnet_id': props['vip_subnet_id'],

KeyError: 'vip_subnet_id'

Using TF UI, Config Editor check all the LB objects and find the LB object which is not complete. For example, Test_LB object is not having vip_subnet_id details.

loadbalancer_properties: {

• admin_state: true

}

For all other objects we can see those details as shown here for Correct_LB object.

loadbalancer_properties: {

• vip_subnet_id: "xxxxxxxxxxxxxxxxxx",
• provisioning_status: "ACTIVE",
• admin_state: true,
• operating_status: "ONLINE",
• vip_address: "10.1.10.1"

}

Solution is to delete the incomplete LB object and re-create the same with full details, if needed. With this config_svcmonitor_1 will become stable.