Build 2738: Alarm config for ANDing of process states of two different processes is not supported

Bug #1600114 reported by Ankit Jain
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Won't Fix
Medium
Sundaresan Rajangam
R3.1
Won't Fix
Medium
Sundaresan Rajangam

Bug Description

I was trying to configure an alarm for the following condition:

Condition: when process1 and process2 are both down then only I should raise an alarm.

Say contrail-dns.state=DOWN AND contrail-named==DOWN -> Raise a configured alarm...

I see the above condition is not configurable with the current alarm implementation.

Please check if we can support this.

I tried the below, this did not help as both the below conditions seem to be same.

and_list:

[
 •
{
 ◦ operation: "!=",
 ◦ operand1: "NodeStatus.process_info.process_state",
 ◦ vars:
[
 ▪ “”contrain-dns"
 ◦ ],
 ◦ operand2: ""PROCESS_STATE_RUNNING""
 • },

[
 •
{
 ◦ operation: "!=",
 ◦ operand1: "NodeStatus.process_info.process_state",
 ◦ vars:
[
 ▪ “”contrain-named"
 ◦ ],
 ◦ operand2: ""PROCESS_STATE_RUNNING""
 • },

Ankit Jain (ankitja)
Changed in juniperopenstack:
importance: Undecided → Medium
Revision history for this message
Sundaresan Rajangam (srajanga) wrote :

Since process_info is a list, we cannot support this configuration. However, we are planning to change process_info to map with process name as the key [for R3.2]. With process_info being a map, you would be able to configure the alarm mentioned in the description.

Changed in juniperopenstack:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.