keda - getting error reading from azure keyvault with context failed

This can be a confusing error from keda. On one hand it is saying unable to read from keyvault while others trigger authentication is able to work without issues. Let's say I have a scaledobject that has 4 event hub scaler configured, two are happy while another 2 are not working. 

All are using the same keyvault and authentication approach. 

When i check keda operator logs i see, "unable to read from keyvault" - yet 2 of those scaler are working. I noticed that the reason it is failing is "context cancelled". This could mean that it failed while performing other operations such as trying to connect to event hub via a specific connection strings. 

After debugging those event hub connection string - i found that the issue is due to this. All i have to do is, do a 

kubectl describe scaledobject/my-scaled-app -n mynamespace

Figure out which event hub scaler that is not working / happy. Then focus on fixing those - instead of trying to review the keda operator logs for clue.

 



Comments

Post a Comment

Popular posts from this blog

gemini cli getting file not defined error

Image
 While trying to run gemini cli on my windows linux subsystem, i bump into this error here - "/Roaming/npm/node_modules/@google/gemini-cli/node_modules/undici/lib/web/webidl/index.js:512 webidl.is.File = webidl.util.MakeTypeAssertion(File)"  "ReferenceError: File is not defined" In Node.js, there’s no built-in File (until very recent Node 20+ with experimental WHATWG APIs). So, unless polyfilled, File is undefined, leading to the ReferenceError. And to resolve this, I had to upgrade to node 22 (might work for node 20) and then I was able to run it.
Read more

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more