Build 2696: Alarms: When agent process state becomes down, all types of vrouter alarms are being raised
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Released
|
Medium
|
Anish Mehta |
Bug Description
1)Alarms of types VrouterInterface, PartialSysinfoC
2) For alarm type VrouterInterface, rule info, operand values are also missing as shown below
"any_of": [
{
"all_of": [ ]
}
],
"severity": 4,
"ack": false,
"timestamp": 1452596857815859,
"token": "eyJ0aW1lc3RhbX
"type": "VrouterInterface"
Pasting the output of http://
{
"NodeStatus":
{
"deleted": false,
"disk_
[
{
"partition_
"partition_
"partition_
"partition_
},
{
}
],
"process_status":
[
{
"state": "Functional",
}
],
"process_info":
[
{
"process_name": "contrail-
"start_count": 1,
"process_
"last_
"core_
"last_
"stop_count": 1,
"last_
"exit_count": 0
},
{
"process_name": "contrail-
"start_count": 1,
"process_
"last_
"core_
"last_
"stop_count": 0,
"last_
"exit_count": 0
},
{
}
]
},
"ContrailConfig":
{
"elements":
[
[
{
"fq_name": "[\"default-
"uuid": "\"bc915855-
"perms2": "{\"owner\": \"ff6dc5c4bedb4
"id_perms": "{\"enable\": true, \"description\": null, \"creator\": null, \"created\": \"2016-
},
"nodeg20:
"nodea21:
],
[
{
},
]
]
},
"UVEAlarms":
{
"alarms":
[
{
"any_of":
[
{
"all_of":
[
{
"json_
"rule":
{
"oper": "==",
"operand1":
{
"keys":
[
]
},
"operand2":
}
]
}
],
"severity": 4,
"ack": false,
"timestamp": 1452596857815492,
"token": "eyJ0aW1lc3RhbX
"type": "PartialSysinfo
},
{
"any_of":
[
{
"all_of":
[
{
"json_
"json_
"rule":
{
"oper": "not in",
"operand1":
{
"keys":
[
"elements",
],
"json": 2
},
"operand2":
{
"keys":
[
]
}
}
},
{
"json_
"json_
"rule":
{
"oper": "!=",
"operand1":
{
"keys":
[
"elements",
],
"json": 2
},
"operand2":
{
"keys":
}
]
}
],
"severity": 3,
"ack": false,
"timestamp": 1452596857815775,
"token": "eyJ0aW1lc3RhbX
"type": "AddressMismatc
},
{
"any_of":
[
{
}
],
"severity": 4,
"ack": false,
"timestamp": 1452596857815859,
"token": "eyJ0aW1lc3RhbX
"type": "VrouterInterface"
},
{
"any_of":
[
{
"all_of":
[
{
"json_
"rule":
{
"oper": "!=",
"operand1":
{
"keys":
[
]
},
"operand2":
{
}
},
"json_vars":
],
}
]
}
}
== Contrail vRouter ==
supervisor-vrouter: active
contrail-
contrail-
== Contrail Control ==
supervisor-control: active
contrail-control active
contrail-
contrail-dns active
contrail-named active
== Contrail Analytics ==
supervisor-
contrail-alarm-gen active
contrail-
contrail-
contrail-collector active
contrail-
contrail-
contrail-topology active
== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-
contrail-
contrail-
contrail-schema backup
contrail-
ifmap active
== Contrail Database ==
contrail-database: active
supervisor-
contrail-
kafka active
== Contrail Support Services ==
supervisor-
rabbitmq-server active
I see the problem with the AddressMismatch Compute alarm.
It should not be raised when the VrouterAgent struct is absent.
For VrouterInterface, I think the plugin is crashing. There should be a message in contrail- alarm-gen. log or contrail- alarm-gen- stdout. log. I will take a look.
Under the current alarm definition, ProcessStatus and PartialSysinfo are valid alams.