Comment 3 for bug 1999690

Reviewed: https://review.opendev.org/c/starlingx/config/+/871393
Committed: https://opendev.org/starlingx/config/commit/be4dce95ffb271a4365b1b938f229691eaba3b62
Submitter: "Zuul (22348)"
Branch: master

commit be4dce95ffb271a4365b1b938f229691eaba3b62
Author: Fabiano Mercer <email address hidden>
Date: Fri Jan 20 22:00:38 2023 -0300

    Create cluster-host-ipAttach all nodes to the cluster host network

    Problem: Nodes in the cluster are attached to the management
    network instead of the cluster host network.

    According to StarlingX documentation, all nodes in the cluster
    must be attached to the cluster host network.
    It is necessary to create the cluster-host for worker or
    storage node before the node_ip is required and just update
    the interface_id field of addresses database when the node's
    interface is being created.

    Test plan ( Debian only )
    PASS Installed 2+1 system using IPv4
         (2controllers, 1 worker)
    PASS Installed 2+1 system using IPv6
         (2controllers, 1 worker)
    PASS AIO-SX system using IPv4
    PASS AIO-SX system using IPv6
    PASS AIO-SX system external access to a Kubernetes service
    PASS AIO-DX system using IPv4 and tested traffic between PODs
    PASS AIO-DX system using IPv6 and tested traffic between PODs
    PASS AIO-SX upgrade
    PASS STANDARD ( 2 controllers + 1 worker ) upgrade
    PASS STANDARD ( 2 controllers + 1 worker ) pod -> external traffic

    Closes-Bug: #1999690

    Signed-off-by: Fabiano Mercer <email address hidden>
    Change-Id: I5aee984269a9710285092d8bc5def0842eb06f9f