user-defined-counters:Alarm profile get attached to all the counters created - expect it to get applied to specific counter
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.1 |
Fix Committed
|
High
|
Sundaresan Rajangam | |||
Trunk |
Fix Committed
|
High
|
Sundaresan Rajangam |
Bug Description
Build R3.1 build 5 Mitaka Ubuntu14.04
1.Created UDC 'vrouter_error'.
2.Attached an alarm profile with the below details
UVEAlarms": {
"alarms": [
{
"severity": 2,
"ack": false,
"timestamp": 1469442913663921,
"alarm_rules": {
"or_list": [
{
"and_list": [
{
"condition": {
"operation": ">=",
"operand1": "UserDefinedCou
"vars": [],
"operand2": "45"
},
"match": [
{
"json_operand1_
"json_vars": {}
}
]
}
]
}
]
},
"token": "eyJ0aW1lc3RhbX
"type": "vrouter",
"description": "vrouter error"
}
3.Created another UDC rule 'api'.As a user dont want the alarm profile ,attached to the "vrouter error" UDC, to be attached to UDC 'api'.But the same rule also got applied,which could be raising false alarm.
There is no way to distinguish multiple UDC while creating alarm.
Changed in juniperopenstack: | |
importance: | Undecided → Critical |
importance: | Critical → High |
assignee: | Raj Reddy (rajreddy) → ted ghose (rintu) |
tags: | added: counters |
information type: | Proprietary → Public |
tags: | added: blocker |
tags: | removed: blocker |
tags: | added: releasenote |
need to add config alarm support to take UVE key