As part of troubleshooting effort for a customer’s issue, we found that reloading BSM daemon from the WebUI is causing the serviceProblem alarm severity to be reset. The severity deviates from what it should to something else upon reloading the daemon.

This is also reproducible in horizon 31 locally in a lab controlled environment. Here’s my observations of reproducing it

• When a business service is associated with multiple ICMP service edges on different nodes

• BS severity is set to match the highest severity of the edges.

• BS is affected by multiple nodes

Attached is the reproduce video, alarmd.log in DEBUG level, events related to BSM states from PostgreSQL