Active controller Install fail due to mgmt addr failed to meet required criteria

[Senthil Mukundakumar]

Brief Description
-----------------

The AIO-SX lab install fails because of the management address range is under 16 addresses.

TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] ***
E fatal: [localhost]: FAILED! => {"changed": false, "msg": "Exception: Failed validation, management address range must contain at least 14 addresses."}

Severity
--------
Major

Steps to Reproduce
------------------
Install AIO-SX

Expected Behavior
------------------
The active controller should be installed and configured successfully

Actual Behavior
----------------
Fail to complete install

Reproducibility
---------------
Reproducible

System Configuration
--------------------
AIO-SX

Lab-name: WCP_122

Branch/Pull Time/Commit
-----------------------
master as of
Load: 2019-10-16_11-52-03

Last Pass
---------
2019-10-09_20-00-00

Test Activity
-------------
Feature Testing

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/689031
Committed: https://git.openstack.org/cgit/starlingx/ansible-playbooks/commit/?id=b68ca0a7ef56d1c9809b45f206ae783bbe2e4b9c
Submitter: Zuul
Branch: master

commit b68ca0a7ef56d1c9809b45f206ae783bbe2e4b9c
Author: David Sullivan <email address hidden>
Date: Wed Oct 16 16:00:01 2019 -0400

    Bootstrap fails due to incorrect minimum range calculations

    The fix for https://bugs.launchpad.net/starlingx/+bug/1845215 introduced
    an issue with the default value for the management_subnet. The minimum
    network range is calculated as the minimum subnet size -2. However for
    many networks we use the default start address as subnet start + 2.

    For now we will update the default management_subnet to be /24 to avoid
    this issue. Another commit will be coming to change the default start
    addresses to subnet start + 1.

    Change-Id: Ic0e93b78288f1e0ceceb068d0b5cae1f1dc75e89
    Partial-Bug: 1848376
    Signed-off-by: David Sullivan <email address hidden>

[Ghada Khalil (gkhalil)]

stx.3.0 / high priority - issue introduced by a recent code change and impacts system installs

[Senthil Mukundakumar (smukunda)]

Verified using 2019-10-16_20-00-00

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/690404

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/690404
Committed: https://git.openstack.org/cgit/starlingx/ansible-playbooks/commit/?id=b6c98196c6a86a682028e1909b3ecdfd3dd24e26
Submitter: Zuul
Branch: master

commit b6c98196c6a86a682028e1909b3ecdfd3dd24e26
Author: David Sullivan <email address hidden>
Date: Wed Oct 16 18:00:35 2019 -0400

    Bootstrap fails due to incorrect minimum range calculations

    The fix for https://bugs.launchpad.net/starlingx/+bug/1845215 exposed
    an issue with the default value for the management_subnet. The minimum
    network range is calculated as the minimum subnet size -2. However for
    many networks we use the default start address as subnet start + 2.

    Here we change the default start addresses to subnet start + 1.

    Closes-Bug: 1848376
    Change-Id: I81aab6e8d60de08dbf27db5b8ff8533104cb4738
    Signed-off-by: David Sullivan <email address hidden>

[Senthil Mukundakumar (smukunda)]

Verified using load 2019-10-20_20-00-00