R3.1 build 6: Alarm Config : Updating operand2 from null to non null is not causing a raised alarm to get cleared

[Ankit Jain]

Updated operand2 in the below rule from null to 'test', but alarm did not get cleared.

rules = {
        "or_list":[
                {
                 "and_list": [
                    {
                     "operand1": "UveVirtualNetworkAgent.mirror_acl",
                     "operand2": "null",
                     "operation": "==",
                     "variables": [],

                     },
                              ]
                 }
                   ]
         }

uve_key = ['virtual-network']

Alarm below got updated, it was supposed to get cleared:

{
alarms: [
{
severity: 6,
ack: false,
timestamp: 1469693719499543,
alarm_rules: {
or_list: [
{
and_list: [
{
condition: {
operation: "==",
operand1: "UveVirtualNetworkAgent.mirror_acl",
vars: [ ],
operand2: "test"
},
match: [
{
json_operand2_value: "null",
json_operand1_value: "null",
json_vars: { }
}
]
}
]
}
]
},
token: "eyJ0aW1lc3RhbXAiOiAxNDY5NjkzNzE5NDk5NTQzLCAiaHR0cF9wb3J0IjogNTk5NSwgImhvc3RfaXAiOiAiNDAuNDMuMS41In0=",
type: "vn",
description: "vn"
}
]
},

[Sundaresan Rajangam (srajanga)]

Since the value of operand2 is not enclosed in double quotes (should have been "\"test"\"), it is considered as a uve attribute and hence evaluated to null. Since operand1 is also "null", the condition matches and hence the alarm is not cleared.