Comment 2 for bug 1435254

Reviewed: https://review.openstack.org/169291
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=2f20ebd0ae36ee7a58892da3aaa981b68ed6f7c7
Submitter: Jenkins
Branch: master

commit 2f20ebd0ae36ee7a58892da3aaa981b68ed6f7c7
Author: Bogdan Dobrelya <email address hidden>
Date: Mon Mar 30 17:27:51 2015 +0200

    Do not re-elect RabbitMQ multistate resource master

    Current monitor action for multistate RabbitMQ resource
    in Pacemaker may re-elect existing master when there is
    no need to do so. That is a problem as master elections
    introduce full cluster downtime and we don't want
    additional elections.

    The fix is to check whether the given node uptime is equal
    to the other nodes uptime and drop this node from the list
    of candidates if there is a master exists. Note, there is a
    special 'rabbit-master' attribute in CIB for this.

    Closes-bug: #1435254

    Change-Id: I6f2484fb8f3284f76461c184148d27aa86a5d4b6
    Signed-off-by: Bogdan Dobrelya <email address hidden>