Back to bug 2149216
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Luis Tomas Bolivar | 2022-11-29 08:42:31 UTC | Assignee | rhos-maint | ltomasbo |
| Keywords | Triaged | |||
| Status | NEW | ASSIGNED | ||
| Target Release | --- | 17.0 | ||
| Priority | unspecified | high | ||
| Target Milestone | --- | z1 | ||
| RHEL Program Management | 2022-11-29 08:42:40 UTC | Target Release | 17.0 --- | --- 17.0 |
| Red Hat One Jira (issues.redhat.com) | 2022-11-29 08:45:03 UTC | Link ID | Red Hat Issue Tracker OSP-20516 | |
| Luis Tomas Bolivar | 2022-11-29 10:17:05 UTC | Link ID | OpenStack gerrit 865909 | |
| Luis Tomas Bolivar | 2023-01-20 10:17:05 UTC | Target Milestone | z1 | beta |
| Target Release | 17.0 | 17.1 | ||
| Jon Uriarte | 2023-02-15 11:29:36 UTC | CC | juriarte | |
| Luis Tomas Bolivar | 2023-02-17 07:24:45 UTC | Link ID | OpenStack gerrit 873860 | |
| Status | ASSIGNED | ON_DEV | ||
| Maysa Macedo | 2023-02-22 13:12:20 UTC | CC | mdemaced | |
| Luis Tomas Bolivar | 2023-02-28 06:56:06 UTC | Link ID | OpenStack gerrit 875598 | |
| Status | ON_DEV | POST | ||
| Luis Tomas Bolivar | 2023-03-03 06:27:08 UTC | Fixed In Version | python-ovn-octavia-provider-1.0.3-1.20230302173806.8aff429.el9osttrunk | |
| Status | POST | MODIFIED | ||
| Lon Hohberger | 2023-03-13 06:01:45 UTC | Fixed In Version | python-ovn-octavia-provider-1.0.3-1.20230302173806.8aff429.el9osttrunk | python-ovn-octavia-provider-1.0.3-1.20230302173806.8aff429.el9ost |
| errata-xmlrpc | 2023-03-13 14:39:46 UTC | Status | MODIFIED | ON_QA |
| Eran Kuris | 2023-03-23 13:13:07 UTC | QA Contact | ekuris | bbonguar |
| Omer Schwartz | 2023-04-05 09:16:40 UTC | CC | oschwart | |
| Status | ON_QA | VERIFIED | ||
| QA Contact | bbonguar | oschwart | ||
| Andy Stillman | 2023-05-26 12:37:59 UTC | Flags | needinfo?(ltomasbo) | |
| Luis Tomas Bolivar | 2023-05-26 13:03:35 UTC | Flags | needinfo?(ltomasbo) | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Doc Text | FIP associated to a LB with HealthMonitors were not included as a new OVN Load Balancer Health Checks. This means that if the VIP is used, traffic will not be redirected to the dead members, but if the FIP is used there is no health checks being applied and traffic will reach dead members. Note a new Load Balancer Health Check is created is created for the FIPs associated to the Load Balancer so that traffic is not redirected to dead members when using the FIP associated to the VIP |
|||
| Jenny-Anne Lynch | 2023-06-02 10:48:36 UTC | Doc Text | FIP associated to a LB with HealthMonitors were not included as a new OVN Load Balancer Health Checks. This means that if the VIP is used, traffic will not be redirected to the dead members, but if the FIP is used there is no health checks being applied and traffic will reach dead members. Note a new Load Balancer Health Check is created is created for the FIPs associated to the Load Balancer so that traffic is not redirected to dead members when using the FIP associated to the VIP | Before this update, Open Virtual Network (OVN) load balancer health checks did not include Floating IPs (FIPs) that were associated to a load balancer with health monitors. If the Virtual IP (VIP) was used, traffic was not redirected to members in the `Error` state. However, if the FIP was used, there was no health check, and traffic reached members in the `Error` state. With this update, there is a new load balancer health check for FIPs associated to the load balancer so that traffic is not redirected to members in the `Error` state when you use the FIP associated to the VIP. |
| CC | jelynch | |||
| mgeary | 2023-06-14 15:04:38 UTC | CC | mgeary | |
| James Smith | 2023-06-14 16:48:18 UTC | Doc Text | Before this update, Open Virtual Network (OVN) load balancer health checks did not include Floating IPs (FIPs) that were associated to a load balancer with health monitors. If the Virtual IP (VIP) was used, traffic was not redirected to members in the `Error` state. However, if the FIP was used, there was no health check, and traffic reached members in the `Error` state. With this update, there is a new load balancer health check for FIPs associated to the load balancer so that traffic is not redirected to members in the `Error` state when you use the FIP associated to the VIP. | Before this update Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) and a Virtual IP (VIP), and traffic was redirected to members in the Error state. + With this update, if you use Floating IPs (FIP) and a Virtual IP (VIP), there is a new load balancer health check , and traffic is not redirected to members in the Error state. |
| Flags | needinfo?(ltomasbo) | |||
| CC | jamsmith | |||
| Luis Tomas Bolivar | 2023-06-15 05:53:30 UTC | Doc Text | Before this update Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) and a Virtual IP (VIP), and traffic was redirected to members in the Error state. + With this update, if you use Floating IPs (FIP) and a Virtual IP (VIP), there is a new load balancer health check , and traffic is not redirected to members in the Error state. | Before this update Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. With this update, if you use Floating IPs (FIP) is associated to the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state. |
| Flags | needinfo?(ltomasbo) | |||
| Roger Heslop | 2023-06-15 13:39:29 UTC | CC | rheslop | |
| James Smith | 2023-06-15 15:19:25 UTC | Doc Text | Before this update Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. With this update, if you use Floating IPs (FIP) is associated to the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state. | Before this update Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. + With this update, if you use Floating IPs (FIP) is associated to the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state. |
| Jenny-Anne Lynch | 2023-07-19 12:14:24 UTC | CC | jelynch | |
| Joanne O'Flynn | 2023-08-10 09:55:52 UTC | Doc Text | Before this update Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. + With this update, if you use Floating IPs (FIP) is associated to the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state. | Before this update, Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. + With this update, if you use Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state. |
| CC | joflynn | |||
| James Smith | 2023-08-13 19:58:55 UTC | Doc Text | Before this update, Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. + With this update, if you use Floating IPs (FIP) associated to the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state. | Before this update, Open Virtual Network (OVN) load balancer health checks were not performed if you used Floating IPs (FIP) associated with the Load Balancer Virtual IP (VIP), and traffic was redirected to members in the Error state if the FIP was used. + With this update, if you use Floating IPs (FIP) associated with the Load Balancer Virtual IP (VIP), there is a new load balancer health check created for the FIP, and traffic is not redirected to members in the Error state. |
| errata-xmlrpc | 2023-08-16 00:04:06 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-16 01:12:44 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-16 01:12:44 UTC | |||
| errata-xmlrpc | 2023-08-16 01:13:02 UTC | Link ID | Red Hat Product Errata RHEA-2023:4577 |
Back to bug 2149216