Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/928335
Committed:
https://opendev.org/openstack/ovn-octavia-provider/commit/6e2ba02339cdb06a63abc74a2b58f993d0560d9c
Submitter: "Zuul (22348)"
Branch: master
commit 6e2ba02339cdb06a63abc74a2b58f993d0560d9c
Author: Fernando Royo <fr...@redhat.com>
Date: Fri Sep 6 12:27:56 2024 +0200
Fix member subnet id on a fully populated LB
When a fully populated LB is created, if the member is not created
indicating the subnet_id to whom it belongs, the LB vip_network_id
is inherit by error as member.subnet_id.
This patch fix this behaviour to inherit the member.subnet_id from
the loadbalancer.vip_subnet_id that is always passed from Octavia
API when call is redirect to the OVN-provider.
Closes-Bug: #2079813
Change-Id: I098afab053119d1a6eac86a12c1a20cc312b06ef
** 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/2079813
Title:
[ovn-octavia-provider] Fully populated LB wrong member subnet id when
not specified
Status in neutron:
Fix Released
Bug description:
When a fully populated LB is created, if the member is not created
indicating the subnet_id to whom it belongs, the LB vip_network_id is
inherit by error as member.subnet_id [1]
If the member subnet_id is indicated in the call or added after LB
creation in a later step this issue is not happening.
[1] https://opendev.org/openstack/ovn-octavia-
provider/blame/commit/0673f16fc68d80c364ed8907b26c061be9b8dec1/ovn_octavia_provider/driver.py#L118
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2079813/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
