management network is not configured for ping test in heat templates

[Bob Fournier]

During the overcloud deployment there is a validation step that checks connectivity between all nodes and controllers. When network isolation is enabled, connectivity checks via ping are done for each of the isolated networks. When the optional management network is added as one of the isolated networks it not being ping tested. This can result in misconfigurations with this network not being detected.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/350787

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/350787
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=12aeac7c849fbcc2ea36635bbd9f653a3f8e092c
Submitter: Jenkins
Branch: master

commit 12aeac7c849fbcc2ea36635bbd9f653a3f8e092c
Author: Bob Fournier <email address hidden>
Date: Wed Aug 3 17:19:21 2016 -0400

    Add management network to list of networks to ping

    Add the end of overcloud deployment, a list of network IP addresses
    for isolated networks is used to check connectivity. The management
    network IP address is missing from this list. This fix adds it in
    so that the management network will be checked if it is configured.

    Change-Id: I02b020681bed7fbd6d05416280d51a2cbcc50eee
    Closes-Bug: 1609554

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 5.0.0.0b3 development milestone.