Bug 1643900
| Summary: | Instances with floating IPs residing on two different subnet with their own routers cannot access each other using FIP on a RHOSP with OVN | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Daniel Alvarez Sanchez <dalvarez> | |
| Component: | python-networking-ovn | Assignee: | Daniel Alvarez Sanchez <dalvarez> | |
| Status: | CLOSED ERRATA | QA Contact: | Roman Safronov <rsafrono> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 14.0 (Rocky) | CC: | apevec, ccopello, dalvarez, ekuris, lhh, lmartins, ltomasbo, majopela, mputhenp, rsafrono | |
| Target Milestone: | z1 | Keywords: | Triaged, ZStream | |
| Target Release: | 14.0 (Rocky) | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | python-networking-ovn-5.0.2-0.20181217155313.726820a.el7ost | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1642830 | |||
| : | 1643902 (view as bug list) | Environment: | ||
| Last Closed: | 2019-03-18 12:57:08 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: | ||||
| Bug Depends On: | 1642830 | |||
| Bug Blocks: | 1643902, 1643905 | |||
|
Description
Daniel Alvarez Sanchez
2018-10-29 12:11:29 UTC
*** Bug 1663265 has been marked as a duplicate of this bug. *** Verified on puddle: 14.0-RHEL-7/2019-02-22.2 rpm: python-networking-ovn-5.0.2-0.20181217155313.726820a.el7ost.noarch Used the following scenario (taken from https://bugzilla.redhat.com/show_bug.cgi?id=1643905#c8 as a reproduction scenario): 1. Created internal network internal_A, subnet_A (192.168.3.0/24), router_A. Connected router_A to the external network. Connected internal network internal_A to the router. Created a VM and connected to the internal_A network. Attached an floating IP to the VM. 2. Created internal network internal_B, subnet_B (192.168.4.0/24), router_B. Connected router_B to the external network. Connected internal network internal_B to the router. Created a VM and connected to the internal_B network. Attached an floating IP to the VM. 3. Tried to ping VMs with floating IPs from external network and from other VM with floating IP. All worked. 4. Deleted one of floating IPs. Then I re-created it again (same ip address, used command 'openstack floating ip create --floating-ip-address 10.0.0.220 nova', 'nova' is external network name) 5. Attached the FIP to the other VM on other internal network, connected to other router. New mac_binding entry in north db was created (OK). Ping and ssh to this VM via FIP worked, arp table on hypevisor was updated with corresponding mac for 10.0.0.220. 6. Created internal network internal_C, subnet_C (192.168.5.0/24), router_C. Connected router_C to the external network. Connected internal network internal_C to the router. Created a VM and connected to the internal_C network. 7. Deleted FIP 10.0.0.220 and recreated it again (see step 4). Then attached it to the VM connected to internal_C network and router_C. 8. Connected to VM on internal_B network (via internal interface in namespace on compute node), tried to ping 10.0.0.220 , ping worked, arp table on hypervisor and ovn mac bindings updated properly. Tested also pings from other VMs (with and without FIPs) to different floating ips, all succeeded. 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, 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/RHBA-2019:0585 |