commit 1d7353352db5a890c9418e9620a690341b0d9add
Author: Fernando Royo <email address hidden>
Date: Wed May 25 14:21:20 2022 +0200
Fix way of calculate LB status after HM event
Function _get_new_operating_statuses was calculating the
LB status based on the received event together with
current operating_status of the members, those values
were not being stored and therefore were not available
for the calculation.
Now those member status are stored in the external_ids
field related to the LB under the neutron:member_status tag,
where the uuid of the member and its current status are
stored.
This way we can calculate the real-time status of the whole
LB hierarchy by looking at the values stored there, which
are updated when HM events are received.
Reviewed: https:/ /review. opendev. org/c/openstack /ovn-octavia- provider/ +/844262 /opendev. org/openstack/ ovn-octavia- provider/ commit/ 1d7353352db5a89 0c9418e9620a690 341b0d9add
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit 1d7353352db5a89 0c9418e9620a690 341b0d9add
Author: Fernando Royo <email address hidden>
Date: Wed May 25 14:21:20 2022 +0200
Fix way of calculate LB status after HM event
Function _get_new_ operating_ statuses was calculating the
LB status based on the received event together with
current operating_status of the members, those values
were not being stored and therefore were not available
for the calculation.
Now those member status are stored in the external_ids member_ status tag,
field related to the LB under the neutron:
where the uuid of the member and its current status are
stored.
This way we can calculate the real-time status of the whole
LB hierarchy by looking at the values stored there, which
are updated when HM events are received.
Partial-Bug: #1965772
Depends-On: https:/ /review. opendev. org/c/openstack /ovn-octavia- provider/ +/844014
Change-Id: I5f5225a94a9a84 01d350d2fda987b f68869def22 dfb429fb4f3e3bb db41c622f7)
(cherry picked from commit c478567b4efb669