Comment 8 for bug 2000071

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/868389
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/509941c6a507872bd6b84ec19cee449e452457af
Submitter: "Zuul (22348)"
Branch: stable/yoga

commit 509941c6a507872bd6b84ec19cee449e452457af
Author: Fernando Royo <email address hidden>
Date: Mon Dec 19 15:36:41 2022 +0100

    Uncouple HM status of member statuses

    When a new HM is created, the provisioning status is conditioned
    by the status of the existing members on the pool. When any of
    the members are in ERROR status (e.g. when a member is configure
    with non existing address) the created HM is in ERROR status.

    It makes more sense to warn about the member problem but let the
    HM continue with its normal flow of operation over the possible
    remaining members that exist for the pool on which it is created.
    This patch removes the break after finding a problematic member
    (port not found) and just log a warning about the issue, but
    continue with the rest of the members.

    Closes-Bug: #2000071
    Change-Id: I5be9130eb63c03d273fc8dfcc93094204a3ed361
    (cherry picked from commit 548d65d1a50612c6b24f85e6ffbdd1cd32bae8e4)