Skip to main content

Tag: Known Problem

This is a documented known problem with known mitigations

IDTitleDescriptionCategoryTechnologyTags
CRE-2024-0007
Critical
Impact: 9/10
Mitigation: 8/10
RabbitMQ Mnesia overloaded recovering persistent queuesThe RabbitMQ cluster is processing a large number of persistent mirrored queues at boot. The underlying Erlang process, Mnesia, is overloaded (`** WARNING ** Mnesia is overloaded`).Message Queue ProblemsrabbitmqKnown ProblemRabbitMQPublic
CRE-2024-0008
High
Impact: 9/10
Mitigation: 6/10
RabbitMQ memory alarmA RabbitMQ node has entered the “memory alarm” state because the total memory used by the Erlang VM (plus allocated binaries, ETS tables, and processes) has exceeded the configured `vm_memory_high_watermark`. While the alarm is active the broker applies flow-control, blocking publishers and pausing most ingress activity to protect itself from running out of RAM.Message Queue ProblemsrabbitmqKnown ProblemRabbitMQPublic
CRE-2024-0016
Low
Impact: 4/10
Mitigation: 2/10
Google Kubernetes Engine metrics agent failing to export metricsThe Google Kubernetes Engine metrics agent is failing to export metrics.Observability Problemsgke-metrics-agentKnown ProblemGKEPublic
CRE-2024-0018
Medium
Impact: 4/10
Mitigation: 5/10
Neutron Open Virtual Network (OVN) high CPU usageOVN daemons (e.g., ovn-controller) are stuck in a tight poll loop, driving CPU to 100 %. Logs show “Dropped … due to excessive rate” or “Unreasonably long … poll interval,” slowing port-binding and network traffic.Networking ProblemsneutronKnown ProblemOvnPublic
CRE-2024-0021
High
Impact: 4/10
Mitigation: 5/10
KEDA operator reconciler ScaledObject panicKEDA allows for fine-grained autoscaling (including to/from zero) for event driven Kubernetes workloads. KEDA serves as a Kubernetes Metrics Server and allows users to define autoscaling rules using a dedicated Kubernetes custom resource definition.Operator ProblemsUnspecifiedKEDACrashKnown ProblemPublic
CRE-2024-0043
Medium
Impact: 6/10
Mitigation: 5/10
NGINX Upstream DNS FailureWhen a NGINX upstream becomes unreachable or its DNS entry disappears, NGINX requests begin to fail.Proxy ProblemsnginxKafkaKnown ProblemPublic
CRE-2025-0025
Medium
Impact: 6/10
Mitigation: 5/10
Kafka broker replication mismatchWhen the configured replication factor for a Kafka topic is greater than the actual number of brokers in the cluster, Kafka repeatedly fails to assign partitions and logs replication-related errors. This results in persistent warnings or an `InvalidReplicationFactorException` when the broker tries to create internal or user-defined topics.Message Queue Problemstopic-operatorKafkaKnown ProblemPublic