You have been subscribed to a public bug:
On 2020-04-09, we discovered that the failover command creates a new LB
instance, kills the old instance (which does not exist), and then fails
to plug a network port as there is already an ovs port on the host for
some reason.
This was discovered during a failed migration attempt using an amphora
image, so an attempt was made to use the failover command. We run the
Octavia loadbalancer with only a single amphora (standalone).
Some of the octavia units were missing the configuration for rabbitmq,
most likely since October 2019, which was fixed when we discovered it.
SEG escalation found the following:
- The duplicate db entry of port bindings causes a `loadbalancer failover` to
fail similarly to what is reported here
- Removing the additional ml2_port_bindings entry does not fix the issue
** Affects: octavia (Ubuntu)
Importance: Undecided
Status: New
** Tags: bootstack
--
octavia loadbalancer refuses to manually failover
https://bugs.launchpad.net/bugs/1878029
You received this bug notification because you are a member of Ubuntu Bugs,
which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
