config nodes connected to both the collectors in the HA setup
Bug #1686862 reported by
Vinoth Kannan Ganapathy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
High
|
Sundaresan Rajangam |
Bug Description
4.0 HA, build 3061
alarm incorrectly reports config nodes are down, from the initial triage, found out that the config node service connected to both the collectors
root@server-
tcp 0 0 192.168.10.3:42250 192.168.10.4:8086 ESTABLISHED 25969/python
tcp 0 0 192.168.10.3:44656 192.168.10.3:8086 ESTABLISHED 25969/python
root@server-
Shown the setup to the Sundar.
Changed in juniperopenstack: | |
importance: | Undecided → High |
description: | updated |
To post a comment you must log in.
sandesh_init() was being called twice resulting in multiple connections to the collector.
The following commit for #1682683 should fix this issue. /github. com/Juniper/ contrail- controller/ commit/ e9a9ef7b3ddd84e c72bed6ab8172b9 642cab2fac
https:/