Update behaviour of NodeStatus UVE for contrail-tor-agent
Contrail-tor-agent currently publishes status as Non-Functional if it is
not connected to any TOR. Analytics module generates alarms when status
is published as Non-Functional. Since contrail-tor-agent has no way to detect
that is is running in backup mode, it is not possible for contrail-tor-agent to
publish status as Functional only in backup mode when it is not connected to
any TOR.
Fix is to publish connection status of contrail-tor-agent without considering its
connection to TOR.
Closes-Bug: 1548050
(cherry picked from commit c8dbbf1e5866a655ae62494a14cb1f1c0b643ace)
Reviewed: https:/ /review. opencontrail. org/17903 github. org/Juniper/ contrail- controller/ commit/ 203b52b6e2527f4 a8482c8f66987fc a07b31d22e
Committed: http://
Submitter: Zuul
Branch: master
commit 203b52b6e2527f4 a8482c8f66987fc a07b31d22e
Author: Ashok Singh <email address hidden>
Date: Fri Feb 26 01:38:48 2016 -0800
Update behaviour of NodeStatus UVE for contrail-tor-agent
Contrail-tor-agent currently publishes status as Non-Functional if it is
not connected to any TOR. Analytics module generates alarms when status
is published as Non-Functional. Since contrail-tor-agent has no way to detect
that is is running in backup mode, it is not possible for contrail-tor-agent to
publish status as Functional only in backup mode when it is not connected to
any TOR.
Fix is to publish connection status of contrail-tor-agent without considering its
connection to TOR.
Closes-Bug: 1548050 5ae62494a14cb1f 1c0b643ace)
(cherry picked from commit c8dbbf1e5866a65
Change-Id: Iee52ea9476f7c7 ea58ccbf33bcc82 e8124be7514