Build 39: Alarms: test_control_alarms failing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
High
|
Nikhil Bansal | ||
R3.0 |
New
|
High
|
Nikhil Bansal |
Bug Description
After stopping contrail-control process alarms below are generated:
Here json operands are null, script checks for the json operands and expects them to be non null.
Expected operands : process name : contral-control, process status : stopped
"control-node":
[
{
"name": "nodeb8",
"value":
{
"UVEAlarms":
{
"alarms":
[
{
"any_of":
[
{
"all_of":
[
{
"json_
"rule":
{
"oper": "==",
"operand1":
{
"keys":
[
]
},
"operand2":
}
]
}
],
"severity": 3,
"ack": false,
"timestamp": 1463726210379328,
"token": "eyJ0aW1lc3RhbX
"type": "ProcessStatus"
},
{
"any_of":
[
{
"all_of":
[
{
"json_
"rule":
{
"oper": "==",
"operand1":
{
"keys":
[
]
},
"operand2":
}
}
]
}
],
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
importance: | Undecided → High |
Changed in juniperopenstack: | |
assignee: | Raj Reddy (rajreddy) → Nikhil Bansal (nikhilb-u) |