yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #88551
[Bug 1964817] Re: [ovn-octavia-provider] Deleted members remain in ERROR status
Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/833799
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/82eabfda244de2de54c8417f201c67129b875199
Submitter: "Zuul (22348)"
Branch: master
commit 82eabfda244de2de54c8417f201c67129b875199
Author: Fernando Royo <froyo@xxxxxxxxxx>
Date: Tue Mar 15 15:36:42 2022 +0100
Fix deletion of members without subnet_id
OVN octavia provider allows to create member without param subnet_id,
in that case the driver search it according to the pool_id, but it is
not propagated to Octavia DB.
In further operations, as delete or update, Octavia call to the driver
without subnet_id, getting as result the member in ERROR state.
Closes-Bug: #1964817
Change-Id: I08b5ee11dbffe672dfd762c944c2f2c18623826f
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1964817
Title:
[ovn-octavia-provider] Deleted members remain in ERROR status
Status in neutron:
Fix Released
Bug description:
An OVN provider Load Balancer allows the creation of members without
specifying the subnet-id. The internal logic allows OVN provider to
create the member by associating it with the subnet-id of the pool to
which it belongs, but the member is stored in Octavia DB without a
reference to the subnet_id associated with the pool.
Subsequently, when an attempt is made to delete a member that was
created without specifying the subnet_id to which it belongs, it is
left in an ERROR state, while a member that did include that parameter
at creation time is deleted correctly.
Steps to Reproduce:
1. Create a load balancer with OVN as provider
2. Create a listener and a pool associated to LB create in 1.
3. Create a member without parameter subnet-id
4. Try to delete the member created in 3.
Expected result:
Member is deleted correctly
Actual result:
Member keeps in ERROR state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1964817/+subscriptions
References