[ovn-octavia-provider] Multivips not linking correctly member to ipv4 and ipv6 VIP

[Fernando Royo]

When a LB is created passing --additional-vips (mixing ipv4 and ipv6) the addition of member are not taking that into account, rejecting the call with following error:

Provider 'ovn' does not support a requested option: OVN provider does not support mixing IPv4/IPv6 configuration within the same Load Balancer. (HTTP 501) (Request-ID: req-1ecd3533-e8fa-4219-a658-c90cd3059fcd)

Additionally once this error is fixed, the vips field need to correlate the IPv4 VIP with IPv4 members and in a similar way for the IPv6 VIP.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/904152

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/904152
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/f469fd83dbe9189821f9344a00b2922799a30795
Submitter: "Zuul (22348)"
Branch: master

commit f469fd83dbe9189821f9344a00b2922799a30795
Author: Fernando Royo <email address hidden>
Date: Wed Dec 20 18:51:05 2023 +0100

    Allow LB members to mix IPv4 and IPv6 for the multivip LB

    When creating a load balancer with both IPv4 and IPv6 protocols
    for the LB VIP and additional_vips field, it is essential to
    allow the mixing of IPv4 and IPv6 backend members.

    This patch enables this use case and ensures that the 'vips'
    field in the OVN NB DB associates IPv4-type LB VIPs with IPv4
    members and IPv6-type LB VIPs with IPv6 members exclusively.

    Closes-Bug: 2047055
    Change-Id: I173a6456e8a5f776cac207390e670afa34f83d7c

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/ovn-octavia-provider 6.0.0.0rc1 release candidate.