Build 2738: Inbuilt alarm config should not be allowed to change
Bug #1599758 reported by
Ankit Jain
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
Won't Fix
|
Medium
|
Sundaresan Rajangam | ||
| R3.1 |
Won't Fix
|
Medium
|
Sundaresan Rajangam | ||
| Trunk |
Won't Fix
|
Medium
|
Sundaresan Rajangam | ||
Bug Description
I think we should not allowed to change the inbuilt alarm config. It should be protected from accidental edition.
Below is the inbuilt alarm where I could update alarm-severity:
alarm: {
display_name: "conf-incorrect",
uuid: "6f9e4eeb-
alarm_rules: {
or_list: [
{
and_list: [
{
operation: "==",
operand1: "ContrailConfig",
vars: [ ],
operand2: "null"
}
]
}
]
},
parent_uuid: "bf12665b-
parent_href: "https:/
parent_type: "global-
alarm_severity: 25,
perms2: {
owner: "b783d71593a54f
owner_access: 7,
global_access: 0,
share: [ ]
},
| information type: | Proprietary → Public |
| Changed in juniperopenstack: | |
| importance: | Undecided → Medium |
Revision history for this message
| Sundaresan Rajangam (srajanga) wrote | #1 |
Revision history for this message
| Sundaresan Rajangam (srajanga) wrote | #2 |
| Changed in juniperopenstack: | |
| status: | New → Won't Fix |
To post a comment you must log in.
With the following commit, the addition of in-built alarms in config has been removed. Will revisit if we add in-built alarms in api-server in the next release.