Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/849691
Committed:
https://opendev.org/openstack/ovn-octavia-provider/commit/136b829579e83618b8497963153edff1de320e6b
Submitter: "Zuul (22348)"
Branch: master
commit 136b829579e83618b8497963153edff1de320e6b
Author: Luis Tomas Bolivar <ltoma...@redhat.com>
Date: Wed Jul 13 16:39:22 2022 +0200
Ensure members without subnet belong to VIP subnet or fail
This patch ensures the members without subnet are only accepted
if the IP of the member belongs to the CIDR of the VIP subnet,
as that is the subnet associated to the loadbalancer used to
obtain the subnet for the members that do not have it.
Closes-Bug: #1982111
Change-Id: I0fd90c9329a2ec43823813542f263845562c45f2
** 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/1982111
Title:
[ovn-octavia-provider] members without subnet wrongly associated to
VIP subnet
Status in neutron:
Fix Released
Bug description:
When members are added without subnet_id information, the ovn-octavia
provider used the VIP subnet for the subnet_id. However, if the member
does not belong to the same subnet as the VIP subnet (i.e., different
cidr), the API does not return any error but there is no connectivity
to the member (as it does not belong to the obtained subnet).
An extra checking to ensure the VIP CIDR includes the member IP should
be done.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1982111/+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
