Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Assignee: Luis Tomas Bolivar (ltomasbo)
Status: In Progress
--
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:
In Progress
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
