[ovn-octavia-provider] restore the member provisioning status to NO_MONITOR after delete the HM

[Fernando Royo]

When a HM is creating over a pool, the members associated to it change theis provisioning_status to ONLINE, and if the health checks packets detects an error on communication it will move to ERROR. When the HM is deleted the provisioning status of those members should come back to NO_MONITOR, but now is keeping on the last status (ONLINE or ERROR)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874609

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874609
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/569c9c011a2cc9e5f041633dde4a47257e4d8565
Submitter: "Zuul (22348)"
Branch: master

commit 569c9c011a2cc9e5f041633dde4a47257e4d8565
Author: Fernando Royo <email address hidden>
Date: Tue Feb 21 16:35:10 2023 +0100

    Reset member provisioning status to NO_MONITOR when a HM is deleted

    At present, when a health monitor (HM) is created for a pool,
    the members of that pool are automatically set to ONLINE
    provisioning status, unless the HM identifies an ERROR during
    health checks.

    This patch addresses an issue where, after deleting an HM,
    the members should be reset to NO_MONITOR provisioning status,
    regardless of whether the HM had previously set them to ONLINE
    or ERROR status.

    Closes-Bug: #2007985
    Change-Id: I02bcba61d0cbc9202a6e50b849f8d781fb825d49

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ovn-octavia-provider 4.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/zed
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/876498

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/yoga
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/876501

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/876506

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/876509

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/876506
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/cbbf3eb5fec4bb141ccfd70665f92591ad4849f6
Submitter: "Zuul (22348)"
Branch: stable/xena

commit cbbf3eb5fec4bb141ccfd70665f92591ad4849f6
Author: Fernando Royo <email address hidden>
Date: Tue Feb 21 16:35:10 2023 +0100

    Reset member provisioning status to NO_MONITOR when a HM is deleted

    At present, when a health monitor (HM) is created for a pool,
    the members of that pool are automatically set to ONLINE
    provisioning status, unless the HM identifies an ERROR during
    health checks.

    This patch addresses an issue where, after deleting an HM,
    the members should be reset to NO_MONITOR provisioning status,
    regardless of whether the HM had previously set them to ONLINE
    or ERROR status.

    Closes-Bug: #2007985
    Change-Id: I02bcba61d0cbc9202a6e50b849f8d781fb825d49
    (cherry picked from commit 569c9c011a2cc9e5f041633dde4a47257e4d8565)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/876509
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/6d99a444cf8d9461592145ee5cf198eb5774afa6
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 6d99a444cf8d9461592145ee5cf198eb5774afa6
Author: Fernando Royo <email address hidden>
Date: Tue Feb 21 16:35:10 2023 +0100

    Reset member provisioning status to NO_MONITOR when a HM is deleted

    At present, when a health monitor (HM) is created for a pool,
    the members of that pool are automatically set to ONLINE
    provisioning status, unless the HM identifies an ERROR during
    health checks.

    This patch addresses an issue where, after deleting an HM,
    the members should be reset to NO_MONITOR provisioning status,
    regardless of whether the HM had previously set them to ONLINE
    or ERROR status.

    Closes-Bug: #2007985
    Change-Id: I02bcba61d0cbc9202a6e50b849f8d781fb825d49
    (cherry picked from commit 569c9c011a2cc9e5f041633dde4a47257e4d8565)

[OpenStack Infra (hudson-openstack)]

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

commit 655a1f576cf4511e49b54b6a219b81f7a04adda0
Author: Fernando Royo <email address hidden>
Date: Tue Feb 21 16:35:10 2023 +0100

    Reset member provisioning status to NO_MONITOR when a HM is deleted

    At present, when a health monitor (HM) is created for a pool,
    the members of that pool are automatically set to ONLINE
    provisioning status, unless the HM identifies an ERROR during
    health checks.

    This patch addresses an issue where, after deleting an HM,
    the members should be reset to NO_MONITOR provisioning status,
    regardless of whether the HM had previously set them to ONLINE
    or ERROR status.

    Closes-Bug: #2007985
    Change-Id: I02bcba61d0cbc9202a6e50b849f8d781fb825d49
    (cherry picked from commit 569c9c011a2cc9e5f041633dde4a47257e4d8565)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/876498
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/0f5e9b3dd4b8ab1d9aa380f6247364d90c01ca7b
Submitter: "Zuul (22348)"
Branch: stable/zed

commit 0f5e9b3dd4b8ab1d9aa380f6247364d90c01ca7b
Author: Fernando Royo <email address hidden>
Date: Tue Feb 21 16:35:10 2023 +0100

    Reset member provisioning status to NO_MONITOR when a HM is deleted

    At present, when a health monitor (HM) is created for a pool,
    the members of that pool are automatically set to ONLINE
    provisioning status, unless the HM identifies an ERROR during
    health checks.

    This patch addresses an issue where, after deleting an HM,
    the members should be reset to NO_MONITOR provisioning status,
    regardless of whether the HM had previously set them to ONLINE
    or ERROR status.

    Closes-Bug: #2007985
    Change-Id: I02bcba61d0cbc9202a6e50b849f8d781fb825d49
    (cherry picked from commit 569c9c011a2cc9e5f041633dde4a47257e4d8565)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ovn-octavia-provider 1.3.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ovn-octavia-provider 3.1.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ovn-octavia-provider 2.1.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ovn-octavia-provider wallaby-eom release.