-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect to rabbitmq #5127
Comments
It looks like the ScaledObject can't find the TriggerAuthentication. However, I tried your settings and it worked fine. Have you tried applying the YAML directly? |
Yes, I apply the YAML directly. But I always see this error log "{"level":"error","ts":"2023-10-26T02:23:52Z","logger":"scale_handler","msg":"error resolving auth params","type":"ScaledObject","namespace":"default","name":"test","scalerIndex":0,"error":"error parsing rabbitmq metadata: no host setting given","stacktrace":"github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).buildScalers\n\t/workspace/pkg/scaling/scalers_builder.go:83\ngithub.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).performGetScalersCache\n\t/workspace/pkg/scaling/scale_handler.go:366\ngithub.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).GetScalersCache\n\t/workspace/pkg/scaling/scale_handler.go:280\ngithub.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).getScaledObjectState\n\t/workspace/pkg/scaling/scale_handler.go:570\ngithub.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).checkScalers\n\t/workspace/pkg/scaling/scale_handler.go:241\ngithub.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).startScaleLoop\n\t/workspace/pkg/scaling/scale_handler.go:180"}" |
@qnapnickchang Can you edit the description of this bug to have those YAML files in a code block, please? That way we can check if there is any issue with formatting. Thanks! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Report
Config:
Expected Behavior
Connect to Rabbitmq and Authentication
Actual Behavior
no host setting given
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.12.0
Kubernetes Version
1.25
Platform
Amazon Web Services
Scaler Details
rabbitmq
Anything else?
No response
The text was updated successfully, but these errors were encountered: