Vighnesh Shenoy

/run-e2e **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/2827482261)

/run-e2e solace* **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/2831407977)

Funny, the solace test seems to run fine on my dev cluster, [pastebin](https://pastebin.mozilla.org/evbmea3Q). @JorTurFer

> > Funny, the solace test seems to run fine on my dev cluster, [pastebin](https://pastebin.mozilla.org/evbmea3Q). @JorTurFer > > could we have any dangling resource in the cluster? I'm on vacations...

The scaled object definition seems to be incorrect. If you want to use connection strings for both the event hub, and the storage account, maybe a definition like follows should...

I am still confused as to whether you're using pod identity or not. You say that you're pod identity but your trigger auth definition does not contain ```yaml podIdentity: provider:...

If the KEDA pod was using pod identity and the context is being cancelled, the error might be related to another issue - https://github.com/kedacore/keda/issues/3296. But going by the updated scaled...

@tomkerkhove I can take them (both event hub and service bus) up next week.

@tomkerkhove The Azure Monitor scaler is also missing an e2e test.

@tomkerkhove @JorTurFer @zroubalik We need to create new issues for scalers that have e2e tests in `ts` in need of migration to `go`, and add them here.