The configuration of the contrail-alarm-gen is missing obligatory host_ip parameter. Because of that alarmpartitions may all be allocated to one node:
curl 127.0.0.1:9081/analytics/uves/analytics-node/*?cfilt=AlarmgenPartition | python -mjson.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 464 0 464 0 0 24105 0 --:--:-- --:--:-- --:--:-- 25777
{
"value": [
{
"name": "node-5.test.domain.local",
"value": {
"AlarmgenPartition": {
"inst_parts": [
{
"instance": "0",
"partitions": []
}
]
}
}
},
{
"name": "node-2.test.domain.local",
"value": {
"AlarmgenPartition": {
"inst_parts": [
{
"instance": "0",
"partitions": [
"0",
"1",
"2",
"3",
"4",
"5",
"6",
"7",
"8",
"9",
"10",
"11",
"12",
"13",
"14"
]
}
]
}
}
},
{
"name": "node-7.test.domain.local",
"value": {
"AlarmgenPartition": {
"inst_parts": [
{
"instance": "0",
"partitions": []
}
]
}
}
}
]
}
which results in analytics providing empty responses on the other nodes:
root@node-2:~# curl http://localhost:9081/analytics/uves/vrouters | python -m json.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 124 100 124 0 0 9220 0 --:--:-- --:--:-- --:--:-- 9538
[
{
"href": "http://localhost:9081/analytics/uves/vrouter/node-3.test.domain.local?flat",
"name": "node-3.test.domain.local"
}
]
root@node-5:~# curl http://localhost:9081/analytics/uves/vrouters
[]
root@node-7:~# curl http://localhost:9081/analytics/uves/vrouters
[]
To fix the bug one has to provide the ip address of the br-mesh interface in the [DEFAULTS] section for /etc/contrail/contrail-alarm-gen.conf:
[DEFAULTS]
host_ip = 10.109.19.7
Fix proposed to branch: master
Review: https:/