(More details on the linked tracker) When using tooz configured with multiple sentinels to coordinate group membership for the ceilometer central (and other) agents the coordinator fails to update to use a new master redis server. This is due to lack of retry logic in tooz.
wasn't this bug targeted for RHOS6 instead of RHOS7?
The upstream fix in tooz that gets failover working has merged: https://git.openstack.org/cgit/openstack/tooz/commit/?id=54d6bb1c94270d2794ecefbcaf3f8832010e3d58 No info yet on when a new tooz release will happen.
There was tooz release on April 13th, 0.13.2, it should solve it.
Punted to A4 as discussed on IRC.
*** Bug 1210500 has been marked as a duplicate of this bug. ***
Tooz requires 2 other rebases to work. It's probably safer to fix this with a backport.
automation passed https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS6/job/rhos-jenkins-rhos-6.0-puddle-rhel-7.2-all-in-one-packstack-nova-flatdhcp-rabbitmq-tempest-git-all/28/ and we verify the fix is in. since the fix is working on RHOS7 and this was a backport job, I am moving this ticket to verify
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1472