Tag: Load Balancer
Problems related to load balancers, such as misrouting, unhealthy backends, or configuration faults
ID | Title | Description | Category | Technology | Tags |
---|---|---|---|---|---|
CRE-2025-0040 Low Impact: 6/10 Mitigation: 4/10 | Neutron Open Virtual Network (OVN) fails to bind logical switch due to race condition during load balancer creation | During load balancer creation or other operations involving logical router and logical switch associations, Neutron OVN may raise a `RowNotFound` exception when attempting to reference a logical switch that has just been deleted. This leads to a port binding failure and a rollback of the affected operation. | Networking Problems | neutron | NeutronOvnOpenstackLoad BalancerLogical SwitchOvsdbKnown IssuePublic |
CRE-2025-0051 High Impact: 9/10 Mitigation: 5/10 | NGINX No Live Upstreams Available | NGINX is reporting that all backend servers in an upstream group are unavailable. This means that NGINX cannot route requests to any of its configured backend servers, resulting in client-facing errors. | Load Balancer Problems | nginx | NginxLoad BalancerUpstream FailureConnectivity |
CRE-2025-0075 Critical Impact: 10/10 Mitigation: 6/10 | Nginx Upstream Failure Cascade Crisis | Detects critical Nginx upstream failure cascades that lead to complete service unavailability. This advanced rule identifies comprehensive upstream failure patterns including DNS resolution failures, connection timeouts, SSL/TLS handshake errors, protocol violations, and server unavailability, followed by HTTP 5xx error responses within a 60-second window. The rule uses optimized regex patterns for maximum detection coverage while maintaining high performance and low false-positive rates. It captures both the root cause (upstream failures) and the user-facing impact (HTTP errors) to provide complete incident context. | load-balancer-problem | nginx | NginxReverse ProxyService OutageHigh AvailabilityLoad BalancerCascading Failure |