When 2 amps were down, the failover flow created the first one and
needed to update both amp to configure VRRP, but as the 2nd was missing,
it was set to ERROR. Then the health-manager could not trigger a
failover becasue amphorae in ERROR are excluded from the automated
failover process.
This commit changes the tasks that must be run on both amphorae during a
failover of one amphora, it doesn't mark the secondary amphora in ERROR
if it is not reachable.
Closes-Bug: #2033734
Change-Id: I4bd027346c61b93b537ab53810c2ecb6160b6be2
(cherry picked from commit 248cf2893ea913a74d870a763802a51586e0f63b)
Reviewed: https:/ /review. opendev. org/c/openstack /octavia/ +/897785 /opendev. org/openstack/ octavia/ commit/ 5622431534d3bf9 b8b71ad8fdb2d74 4f94625ec4
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.2
commit 5622431534d3bf9 b8b71ad8fdb2d74 4f94625ec4
Author: Gregory Thiemonge <email address hidden>
Date: Mon Sep 4 05:56:25 2023 -0400
Fix amphorae in ERROR during the failover
When 2 amps were down, the failover flow created the first one and
needed to update both amp to configure VRRP, but as the 2nd was missing,
it was set to ERROR. Then the health-manager could not trigger a
failover becasue amphorae in ERROR are excluded from the automated
failover process.
This commit changes the tasks that must be run on both amphorae during a
failover of one amphora, it doesn't mark the secondary amphora in ERROR
if it is not reachable.
Closes-Bug: #2033734
Change-Id: I4bd027346c61b9 3b537ab53810c2e cb6160b6be2 74d870a763802a5 1586e0f63b)
(cherry picked from commit 248cf2893ea913a