Build 2738: Alarm config: Raised alarm not getting cleared/updated as per new rule when alarm rule config gets updated

Bug #1599749 reported by Ankit Jain
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Released
High
Sundaresan Rajangam

Bug Description

Initial config for the alarm below:

{
alarm: {
display_name: "test6",
uuid: "47d753e5-42d7-4e54-a8d0-e133c561bfa9",
alarm_rules: {
or_list: [
{
and_list: [
{
operation: ">=",
operand1: "NodeStatus.process_info.start_count",
vars: [
"NodeStatus.process_info.process_name"
],
operand2: "5"
}
]
}
]
},
parent_uuid: "bf12665b-8819-429a-9280-3d45c5890e30",
parent_href: "https://nodeg13:8143/proxy?proxyURL=http://10.204.217.60:9100/global-system-config/bf12665b-8819-429a-9280-3d45c5890e30",
parent_type: "global-system-config",
alarm_severity: 7,
perms2: {
owner: "b783d71593a54f748f681a1e9a86fef1",
owner_access: 7,
global_access: 0,
share: [ ]
},
href: "https://nodeg13:8143/proxy?proxyURL=http://10.204.217.60:9100/alarm/47d753e5-42d7-4e54-a8d0-e133c561bfa9",
id_perms: {
enable: true,
uuid: {
uuid_mslong: 5176698540819698000,
uuid_lslong: 12164470205998810000
},
creator: null,
created: "2016-07-07T07:23:09.385349",
user_visible: true,
last_modified: "2016-07-07T07:29:07.339225",
permissions: {
owner: "admin",
owner_access: 7,
other_access: 7,
group: "_member_",
group_access: 7
},
description: "my-type6"
},
fq_name: [
"default-global-system-config",
"my-type6"
],
uve_keys: [
"analytics-node",
"control-node"
],
name: "my-type6"
}
}

Below Alarm got raised for this as per the matched condition :

{
severity: 7,
ack: false,
timestamp: 1467876211722431,
alarm_rules: {
or_list: [
{
and_list: [
{
condition: {
operation: ">=",
operand1: "NodeStatus.process_info.start_count",
vars: [ ],
operand2: "5"
},
match: [
{
json_operand1_value: "7",
json_vars: { }
},
{
json_operand1_value: "8",
json_vars: { }
}
]
}
]
}
]
},
token: "eyJ0aW1lc3RhbXAiOiAxNDY3ODc2MjExNzIyNDMxLCAiaHR0cF9wb3J0IjogNTk5NSwgImhvc3RfaXAiOiAiMTAuMjA0LjIxNy41MyJ9",
type: "my-type6"
}

Steps:

1) Updated the alarm rule in initial config with new rule shown below:

alarm_rules: {
or_list: [
{
and_list: [
{
operation: ">=",
operand1: "NodeStatus.process_info.start_count",
vars: [
"NodeStatus.process_info.process_name"
],
operand2: "10"
}
]
}
]
}

With the new rule, alarm raised is no longer valid and should get cleared but it did not happen

Revision history for this message
Sundaresan Rajangam (srajanga) wrote :

https://review.opencontrail.org/#/c/21280/
This patch should handle the alarm config update. This patch is already merged.
Please test with the latest build.

information type: Proprietary → Public
Changed in juniperopenstack:
importance: Undecided → High
Revision history for this message
aswani kumar (aswanikumar90) wrote :

fix verified
working

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.