Before adding support for lbs with VIPs on the provider networks, there was no need to react to gateway chassis creation events, and nothing was done for its deletion. However, after adding the support for that, there is a need of properly handling the creation event for that type of port. The LogicalRouterPortEvent for gateway_chassis port are skip [1], however if ovn lb VIPs are on provider network, the create event needs to be handle so that the loadbalancer gets properly configured and added to the router For the loadbalancer VIPs on the provider network, processing the event and triggering the lb_creat_lrp_assoc_handler means that the information about the logical router will be added, i.e., the router is added to the loadbalancer external_ids as a lr_ref, while the loadbalancer is also added into the logical_router object (loadbalancer entry). In addition, the lb is also added to the logical switches connected to the router. [1] https://opendev.org/openstack/ovn-octavia-provider/src/commit/acbf6e7f3e223c088582390475c84464bc27227d/ovn_octavia_provider/event.py#L39
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577