Comment 15 for bug 1491306

Reviewed: https://review.openstack.org/239448
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=e052a2d5cf2d313853b472b971033f1c83c4d55c
Submitter: Jenkins
Branch: stable/6.1

commit e052a2d5cf2d313853b472b971033f1c83c4d55c
Author: Bogdan Dobrelya <email address hidden>
Date: Thu Sep 3 13:53:13 2015 +0200

    Detect a last man standing for rabbit OCF agent

    W/o this patch, the race condition is possible
    when there is no running rabbit nodes/resource
    master. The rabbit nodes will start/stop in an
    endless loop as a result introducing full downtime
    for AMQP cluster and cloud control plane.

    The solution is:
    * On post-start/post-promote notify, do nothing, if
      either of the following is a true:
      - there is no rabbit resources running or no master
      - the list of rabbit resources being started/promoted
        reported empty
    * For such cases, do not report resource failure and delegate
      recovery, if needed, to the "running out of the cluster"
      monitor's logic.
    * Additionally, report about a last man standing when
      there is no running rabbit resources around.

    Closes-bug: #1491306

    Conflicts:
     files/fuel-ha-utils/ocf/rabbitmq

    Change-Id: If1c62fac26b63410636413c49fce55c35e53dc5f