Back to bug 2160481
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Eduardo Olivares | 2023-01-12 15:00:45 UTC | Comment | 0 | updated |
| Red Hat One Jira (issues.redhat.com) | 2023-01-12 15:00:53 UTC | Link ID | Red Hat Issue Tracker OSP-21358 | |
| Luis Tomas Bolivar | 2023-01-25 07:25:31 UTC | Keywords | FutureFeature, RFE | |
| Summary | ovn-bgp-agent does not support FIP port forwarding yet | [RFE] ovn-bgp-agent does not support FIP port forwarding yet | ||
| CC | ltomasbo | |||
| Candido Campos | 2023-05-10 11:12:37 UTC | QA Contact | ekuris | ccamposr |
| CC | ccamposr | |||
| Greg Rakauskas | 2023-06-02 18:21:57 UTC | Doc Text | In Red Hat OpenStack Platform (RHOSP) 17.1 environments that use BGP dynamic routing, there is currently a known issue where forwarding to ports on floating IP (FIP) addresses fail. Instead, the network traffic intended for the FIPs is being forwarded to a tenant port IP address that is contained on the list of ports configured to perform the port forwarding. The cause for this failure is that the OVN BGP agent is not exposing routes to FIPs. Currently, there is no workaround. | |
| Doc Type | If docs needed, set a value | Known Issue | ||
| CC | gregraka | |||
| Greg Rakauskas | 2023-06-02 18:23:32 UTC | Flags | needinfo?(eolivare) | |
| Eduardo Olivares | 2023-06-05 13:03:09 UTC | Flags | needinfo?(eolivare) | |
| Greg Rakauskas | 2023-06-13 20:49:42 UTC | Doc Text | In Red Hat OpenStack Platform (RHOSP) 17.1 environments that use BGP dynamic routing, there is currently a known issue where forwarding to ports on floating IP (FIP) addresses fail. Instead, the network traffic intended for the FIPs is being forwarded to a tenant port IP address that is contained on the list of ports configured to perform the port forwarding. The cause for this failure is that the OVN BGP agent is not exposing routes to FIPs. Currently, there is no workaround. | In Red Hat OpenStack Platform (RHOSP) 17.1 environments that use BGP dynamic routing, there is currently a known issue where floating IP (FIP) port forwarding fails. + When FIP port forwarding is configured, packets sent to a specific destination port with a destination IP that equals the FIP are redirected to an internal IP from a RHOSP Networking service (neutron) port. This occurs regardless of the protocol that is used: TCP, UDP, and so on. + When BGP dynamic routing is configured, the routes to the FIPs used to perform FIP port forwarding are not exposed, and these packets cannot reach their final destinations. + Currently, there is no workaround. |
| Flags | needinfo?(eolivare) | |||
| Target Milestone | --- | ga | ||
| Eduardo Olivares | 2023-06-15 14:19:05 UTC | Target Milestone | ga | z1 |
| Flags | needinfo?(eolivare) | needinfo?(ltomasbo) | ||
| Luis Tomas Bolivar | 2023-06-15 17:20:07 UTC | Flags | needinfo?(ltomasbo) | |
| Ian Frangs | 2023-08-03 15:46:23 UTC | CC | rhos-maint | |
| Flags | needinfo?(rhos-maint) | |||
| Jenny-Anne Lynch | 2023-08-10 09:12:15 UTC | CC | jelynch | |
| Doc Text | In Red Hat OpenStack Platform (RHOSP) 17.1 environments that use BGP dynamic routing, there is currently a known issue where floating IP (FIP) port forwarding fails. + When FIP port forwarding is configured, packets sent to a specific destination port with a destination IP that equals the FIP are redirected to an internal IP from a RHOSP Networking service (neutron) port. This occurs regardless of the protocol that is used: TCP, UDP, and so on. + When BGP dynamic routing is configured, the routes to the FIPs used to perform FIP port forwarding are not exposed, and these packets cannot reach their final destinations. + Currently, there is no workaround. | In RHOSP 17.1 environments that use BGP dynamic routing, there is currently a known issue where floating IP (FIP) port forwarding fails. + When FIP port forwarding is configured, packets sent to a specific destination port with a destination IP that equals the FIP are redirected to an internal IP from a RHOSP Networking service (neutron) port. This occurs regardless of the protocol that is used: TCP, UDP, and so on. + When BGP dynamic routing is configured, the routes to the FIPs used to perform FIP port forwarding are not exposed, and these packets cannot reach their final destinations. + Currently, there is no workaround. |
||
| Mike Burns | 2023-08-11 13:59:33 UTC | Target Milestone | z1 | z2 |
Back to bug 2160481