Build 2738: Alarm config: Raised alarm not getting cleared/updated as per new rule when alarm rule config gets updated
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-
alarm_rules: {
or_list: [
{
and_list: [
{
operation: ">=",
operand1: "NodeStatus.
vars: [
"NodeStatus.
],
operand2: "5"
}
]
}
]
},
parent_uuid: "bf12665b-
parent_href: "https:/
parent_type: "global-
alarm_severity: 7,
perms2: {
owner: "b783d71593a54f
owner_access: 7,
global_access: 0,
share: [ ]
},
href: "https:/
id_perms: {
enable: true,
uuid: {
uuid_mslong: 517669854081969
uuid_lslong: 121644702059988
},
creator: null,
created: "2016-07-
user_visible: true,
last_modified: "2016-07-
permissions: {
owner: "admin",
owner_access: 7,
other_access: 7,
group: "_member_",
group_access: 7
},
description: "my-type6"
},
fq_name: [
"default-
"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.
vars: [ ],
operand2: "5"
},
match: [
{
json_operand1_
json_vars: { }
},
{
json_operand1_
json_vars: { }
}
]
}
]
}
]
},
token: "eyJ0aW1lc3RhbX
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.
vars: [
"NodeStatus.
],
operand2: "10"
}
]
}
]
}
With the new rule, alarm raised is no longer valid and should get cleared but it did not happen
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.