Bug 2160469

Summary: sync removes the route to a FIP when the corresponding subnet network has dhcp disabled
Product: Red Hat OpenStack Reporter: Eduardo Olivares <eolivare>
Component: ovn-bgp-agentAssignee: Luis Tomas Bolivar <ltomasbo>
Status: CLOSED ERRATA QA Contact: Eduardo Olivares <eolivare>
Severity: high Docs Contact:
Priority: high    
Version: 17.1 (Wallaby)CC: dalvarez, lmartins, ltomasbo
Target Milestone: betaKeywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovn-bgp-agent-0.3.1-1.20230120160941.62a04d4.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 01:13:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eduardo Olivares 2023-01-12 14:16:04 UTC 
Description of problem:
This bug is reproduced by executing the upstream test test_mac_learning_vms_on_same_network from neutron-tempest-plugin on an OSP environment with BGP configured.

That test creates a VM with a port connected to a tenant network, with an IPv4 subnet with dhcp disabled. The VM is created with config_drive set to True.
In that case, the port_binding entry from the OVN SBDB corresponding to the tenant port, is created with mac=unknown
When this happens, when the VM is created and a FIP is attached to it, the FIP route is initially exposed, but some time later, when the sync process is executed, it removes that route, which is obviously wrong.




Version-Release number of selected component (if applicable):
RHOS-17.1-RHEL-9-20221130.n.1
ovn-bgp-agent-0.3.1-1.20221117171123.5388639.el9ost.noarch


How reproducible:
100%

Steps to Reproduce:
run test test_mac_learning_vms_on_same_network
or follow the steps described above

Actual results:
no connectivity to the FIP

Expected results:
connectivity to the FIP
Comment 15 errata-xmlrpc 2023-08-16 01:13:15 UTC 
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