You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Azure Eventhub Scaler creates a storage path with url.parse() based on information from an eventhub connection string. If this connection string contains invalid characters like newline, the url.parse raise an error. This error is unhandled, so the operator crashes with a panic.
Invalid characters usually appear if the connectionstring contains an incorrect base64 encoding.
Expected Behavior
the Azure Eventhub Scaler should log an error message, which contains informations about the incorrect connectionstring
Actual Behavior
the keda operator get a panic
Steps to Reproduce the Problem
add an Azure Eventhub scaler
add an Azure Eventhub connectionstring with a newline character
the keda operator crash with a panic
Logs from KEDA operator
No response
KEDA Version
2.7.1
Kubernetes Version
No response
Platform
No response
Scaler Details
Eventhub Scaler
Anything else?
No response
The text was updated successfully, but these errors were encountered:
zroubalik
changed the title
Keda operator crashes on nil memory panic if the eventhub connectionstring for eventhub scaler contains an invalid character
KEDA operator crashes on nil memory panic if the eventhub connectionstring for Azure Eventhub Scaler contains an invalid character
May 30, 2022
Report
The Azure Eventhub Scaler creates a storage path with
url.parse()
based on information from an eventhub connection string. If this connection string contains invalid characters like newline, theurl.parse
raise an error. This error is unhandled, so the operator crashes with a panic.Invalid characters usually appear if the connectionstring contains an incorrect base64 encoding.
Expected Behavior
the Azure Eventhub Scaler should log an error message, which contains informations about the incorrect connectionstring
Actual Behavior
the keda operator get a panic
Steps to Reproduce the Problem
Logs from KEDA operator
No response
KEDA Version
2.7.1
Kubernetes Version
No response
Platform
No response
Scaler Details
Eventhub Scaler
Anything else?
No response
The text was updated successfully, but these errors were encountered: