Impact status calculated wrong on OS cluster.


The impact calculation calculates the incorrect severity for business services containing OS cluster.

Steps to Reproduce

Create BS with OS cluster (one is HOST and one CONTAINMENT) the HOST should be connected with another CI.
Send alert on the HOST CI, update the alert or change its severity, the impact of the CI parents should be calculated wrong (check on EM Dashbord)

1. Deploy OS Cluster Example
2. Create tomcat CI
3. Add this tomcat CI to the map (right click and Add CI)
4. Create new rel on cmdb_rel_ci table:
parent: the tomcat ci you just created
type: Runs on::Runs
child: Server Node of the OS cluster
4. Send alert on Server Node of the OS cluster


This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

At this moment there is no other workaround apart from the versions in which this is fixed.

Related Problem: PRB1350076