Let IP range validation fail instead of outputting warnings

[Florian Fuchs]

The validation that checks the ctlplane IP range currently fails only if the number of IPs is illogical (start IP higher than end IP) but not if the number of available IPs is lower than the recommended 25 IPs (it succeeds with warnings in that case). This can be confusing, so the validation should fail in the latter case as well.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/498443
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=940096d719dd6c19899a89a23c532ce9161c65ea
Submitter: Zuul
Branch: master

commit 940096d719dd6c19899a89a23c532ce9161c65ea
Author: Florian Fuchs <email address hidden>
Date: Mon Aug 28 11:57:53 2017 +0200

    Let the IP range validation fail on low IP range

    The validation that checks the number of available IPs on the ctlplane
    currently succeeds with warnings if the number is too low.

    This patch makes the validation fail if the IP range is below the
    recommended minimum.

    Change-Id: I40b8a34631086cfe8481b8f2acee84461ad3dafe
    Closes-Bug: #1713483

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-validations 8.0.0 release.