haproxy config fails when containers are missing

[Kevin Carter]

The basic haproxy configuration file found here [ https://github.com/openstack/openstack-ansible/blob/master/playbooks/vars/configs/haproxy_config.yml ] needs to to have the backend entries with a default value of a list. This is needed when using the haproxy role in a n environment that is not an All in one and is using pieces of a OSA and a partial inventory as set in the user configuration files. To fix this eacho of the backend names should have a list entry as the default.

[OpenStack Infra (hudson-openstack)]

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

commit 589650228bb2678487b5750688fe403095955db7
Author: Kevin Carter <email address hidden>
Date: Thu Nov 5 06:48:41 2015 -0600

    Fixed haproxy backend config issue

    The change updates the haproxy configs to use backends with a
    default of an empty array. This is needed to ensure that the backends
    are not being assumed to have some value. In the current system if an
    inventory item did not exist the rendered backend would be a jinja
    string which would cause the haproxy play to fail.

    Closes-Bug: #1513455

    Change-Id: I221dbd910c75c2e41c98a33e1c38c7f69718b544
    Signed-off-by: Kevin Carter <email address hidden>

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: liberty
Review: https://review.openstack.org/245883

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/245883
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=d9dd18f9664c911c4fc936ac4ca5372b0f40364c
Submitter: Jenkins
Branch: liberty

commit d9dd18f9664c911c4fc936ac4ca5372b0f40364c
Author: Kevin Carter <email address hidden>
Date: Thu Nov 5 06:48:41 2015 -0600

    Fixed haproxy backend config issue

    The change updates the haproxy configs to use backends with a
    default of an empty array. This is needed to ensure that the backends
    are not being assumed to have some value. In the current system if an
    inventory item did not exist the rendered backend would be a jinja
    string which would cause the haproxy play to fail.

    Closes-Bug: #1513455

    Change-Id: I221dbd910c75c2e41c98a33e1c38c7f69718b544
    Signed-off-by: Kevin Carter <email address hidden>
    (cherry picked from commit 589650228bb2678487b5750688fe403095955db7)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: kilo
Review: https://review.openstack.org/253180

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/253180
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=19d00527dd2cfbd1db1360e183a5dab7a2fab0b1
Submitter: Jenkins
Branch: kilo

commit 19d00527dd2cfbd1db1360e183a5dab7a2fab0b1
Author: Kevin Carter <email address hidden>
Date: Thu Nov 5 06:48:41 2015 -0600

    Fixed haproxy backend config issue

    The change updates the haproxy configs to use backends with a
    default of an empty array. This is needed to ensure that the backends
    are not being assumed to have some value. In the current system if an
    inventory item did not exist the rendered backend would be a jinja
    string which would cause the haproxy play to fail.

    Closes-Bug: #1513455

    Change-Id: I221dbd910c75c2e41c98a33e1c38c7f69718b544
    Signed-off-by: Kevin Carter <email address hidden>
    (cherry picked from commit 589650228bb2678487b5750688fe403095955db7)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 12.0.8 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 12.0.9 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 12.0.11 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.15 release.