keepalived enters FAULT state when public internet is not pingable from management network

[Greg Faust]

when the ping check fails, keepalived enters a FAULT state:

https://github.com/openstack/openstack-ansible/blob/master/playbooks/vars/configs/keepalived_haproxy.yml#L34

https://github.com/evrardjp/ansible-keepalived/blob/master/templates/keepalived.conf.j2#L38

in my environment the public internet is not pingable from the management network.

It seems unreasonable to assume that the public internet is pingable.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/305971
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=ae99efd64c367108075df6930f9a66b3c979b8e6
Submitter: Jenkins
Branch: master

commit ae99efd64c367108075df6930f9a66b3c979b8e6
Author: Jean-Philippe Evrard <email address hidden>
Date: Thu Apr 14 17:14:19 2016 +0100

    Adding modularity to keepalived configuration

    This patch introduces modularity into the default keepalived
    configuration: Currently, keepalived uses a ping to check its
    alive status. The IP was hard setted in the configuration file.

    This patch introduces multiple variables:
    - keepalived_ping_address
    - keepalived_ping_count
    - keepalived_ping_interval

    The one probably used the most will be the
    ``keepalived_ping_address``. It's therefore listed in
    ``user_variables`` with the other keepalived variables.

    Fixes-Bug: #1570420

    Change-Id: Ic9a591fe739dd4ee3b0ad0130190e000404fb73a

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/307680

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/307680
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=a27c1e4b6386f782e8813d5615ba8159fee74ada
Submitter: Jenkins
Branch: stable/mitaka

commit a27c1e4b6386f782e8813d5615ba8159fee74ada
Author: Jean-Philippe Evrard <email address hidden>
Date: Thu Apr 14 17:14:19 2016 +0100

    Adding modularity to keepalived configuration

    This patch introduces modularity into the default keepalived
    configuration: Currently, keepalived uses a ping to check its
    alive status. The IP was hard setted in the configuration file.

    This patch introduces multiple variables:
    - keepalived_ping_address
    - keepalived_ping_count
    - keepalived_ping_interval

    The one probably used the most will be the
    ``keepalived_ping_address``. It's therefore listed in
    ``user_variables`` with the other keepalived variables.

    Fixes-Bug: #1570420

    Change-Id: Ic9a591fe739dd4ee3b0ad0130190e000404fb73a
    (cherry picked from commit ae99efd64c367108075df6930f9a66b3c979b8e6)