Hide Forgot
Description of problem (clone of upstream bug): =============================================== While having 2 instances of aodh-evaluator strange behavior is observed in logs: - some alarms might be skipped by both evaluators - some alarms might be evaluated by both evaluators - all alarms are skipped by both evaluaotors Coordination backend - redis. Both evaluator are working as expected when just one instance is running. Both running on different nodes. Version-Release number of selected component (if applicable): ============================================================= openstack-aodh-common-1.1.2-1.el7ost.noarch openstack-aodh-notifier-1.1.2-1.el7ost.noarch openstack-aodh-api-1.1.2-1.el7ost.noarch openstack-aodh-compat-1.1.2-1.el7ost.noarch openstack-aodh-listener-1.1.2-1.el7ost.noarch openstack-aodh-evaluator-1.1.2-1.el7ost.noarch openstack-aodh-expirer-1.1.2-1.el7ost.noarch python-aodh-1.1.2-1.el7ost.noarch redis-2.8.24-1.el7ost.x86_64 python-redis-2.10.3-3.el7ost.noarch python-tooz-1.24.0-1.el7ost.noarch
Backport upstream for Mitaka is at https://review.openstack.org/319303
Backported to Liberty https://review.openstack.org/326573
Verified with: -------------- openstack-aodh-api-2.0.3-2.el7ost.noarch openstack-aodh-common-2.0.3-2.el7ost.noarch openstack-aodh-evaluator-2.0.3-2.el7ost.noarch openstack-aodh-listener-2.0.3-2.el7ost.noarch python-aodh-2.0.3-2.el7ost.noarch python-aodhclient-0.5.0-1.el7ost.noarch openstack-aodh-notifier-2.0.3-2.el7ost.noarch