[ovn-octavia-provider] gateway chassis not filled on LogicalRouterPort event

[Fernando Royo]

The gateway neutron-ovn-invalid-chassis previously used for the CR-LRP gateway_chassis has been removed in [1]. At this way, the logical router port event received at creation is considered as a new port attached to the router to a tenant network, adding the LB to that LS, which results in failure during the functional tests.

In a real environment, this situation may not occur, except in the scenario where the gateway_chassis for the LRP would arrive in a second event rather than in the initial creation event.

[1] https://review.opendev.org/c/openstack/neutron/+/909305

[OpenStack Infra (hudson-openstack)]

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

commit eb5010f8ec27c61a3455d09f14057e29cd387f05
Author: Fernando Royo <email address hidden>
Date: Thu Mar 7 13:01:51 2024 +0100

    Fix check for a CR-LRP as a gateway port

    As per [1], the gateway neutron-ovn-invalid-chassis previously
    used for the CR-LRP gateway_chassis has been removed. However,
    it is necessary to determine whether a Logical Router Port (LRP)
    is a gateway port or not to appropriately assign the Load
    Balancer (LB) to the Logical Switch (LS) associated with tenant
    and provider networks.

    This patch modifies the logic within the LogicalRouterPortEvent
    to examine the external_ids and determine if the port is a
    gateway port or not, regardless of whether gateway_chassis is
    included or not.

    [1] https://review.opendev.org/c/openstack/neutron/+/909305

    Closes-Bug: #2056537

    Change-Id: I05bc97362e45a0239cf9206ba8539fcfb10a1151

[OpenStack Infra (hudson-openstack)]

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