Build 2738: Invalid alarm configuration should not be allowed
Bug #1599733 reported by
Ankit Jain
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.1 |
Won't Fix
|
High
|
Sundaresan Rajangam | |||
Trunk |
Fix Committed
|
High
|
Sundaresan Rajangam |
Bug Description
I tried couple of invalid configurations mentioned below and was able to generate alarm configuration successfully.
Configuring invalid severity:
Out of range 10 -> accepted
String : 'abc' -> accepted
----
parent_type: "global-
alarm_severity: "abc",
perms2: {
owner: "b783d71593a54f
owner_access: 7,
global_access: 0,
share: [ ]
Configuring invalid uve keys :
uve_keys: [
"abc",
"abc"
],
name: "my-type1"
}
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
importance: | Undecided → Medium |
tags: | added: releasenote |
To post a comment you must log in.
I think this should also not be allowed :
When uve_keys: [
"analytics-node",
"control-node"
] and parent obj is of type 'project'
Please check
alarm: { b547-4870- ad2a-dbb1840139 68", process_ info.process_ state", process_ info.process_ name" STATE_RUNNING" " 0bff-4afa- bc39-c64ff229fd fb", /nodeg13: 8143/proxy? proxyURL= http:// 10.204. 217.53: 9100/project/ 2768bf1f- 0bff-4afa- bc39-c64ff229fd fb", /nodeg13: 8143/proxy? proxyURL= http:// 10.204. 217.53: 9100/alarm/ 66c56bd1- b547-4870- ad2a-dbb1840139 68",
display_name: "test3",
uuid: "66c56bd1-
alarm_rules: {
or_list: [
{
and_list: [
{
operation: "!=",
operand1: "NodeStatus.
vars: [
"NodeStatus.
],
operand2: ""PROCESS_
}
]
}
]
},
parent_uuid: "2768bf1f-
parent_href: "https:/
parent_type: "project",
alarm_severity: 2,
perms2: {},
href: "https:/
id_perms: {},
fq_name: [
"default-domain",
"admin",
"type3"
],
uve_keys: [
"analytics-node",
"control-node"
],
name: "type3"