[neutron lbaasv2] ip and subnet is dismatched when creating pool-member

[QingchuanHao]

when creating a pool-member, neutron lbaasv2 do not verify whether IP is valid on the subnet.

[Akihiro Motoki (amotoki)]

Octavia project maintains neutron-lbaas repo now.
Targeting the bug to Octavia

[Reedip (reedip-banerjee-deactivatedaccount)]

Hi, can you add some more information, like:
- Steps executed
- Actual result
- Observed result etc?

[Michael Johnson (johnsom)]

This is by design. There are valid use cases where the IP specified for a member is routable from the subnet specified for the member. This means you cannot always assume the member IP is from the subnet specified.

[QingchuanHao (haoqingchuan-28)]

@MJ, but routeable from the subnet is not implemented, right?
1. Take haproxy driver for example, the route exists in haproxy namespace is only that created by the vip port subnet. It has nothing to do with subnet.
2. Is it suitable, ease of use for end user to implement that cases you mention? and what cases invovled?
Thanks you very much, MJ.

[Michael Johnson (johnsom)]

The old haproxy namespace driver is deficient in a number of ways. It may not support subnets with routes.
Frankly we should probably start deprecation on that driver.
That said, other drivers do support routes on subnets so we should not restrict those because an old driver does not support it.
Support for this came in because a large ISP needed it for their deployment.

[Michael Johnson (johnsom)]

See: https://developer.openstack.org/api-ref/networking/v2/?expanded=create-subnet-detail#create-subnet
"host routes"

[OpenStack Infra (hudson-openstack)]

Change abandoned by QingchuanHao ([e-mail]) on branch: stable/ocata
Review: https://review.openstack.org/458138