KEDA Event-Hub Scaler is not looking for the same checkpoint blob path as Spring Cloud Azure Event Hub Stream Binder

[avpines]

Spring Cloud Azure Event Hub Stream Binder made changes to how they are creating the checkpoint blob when moving from release 1.2.2 to 1.2.3, probably to be consistent with other checkpoint path format.

The format that is created is blobContainerName/<EVENTHUB_NAMESPACE>.servicebus.windows.net/<EVENTHUB>/$default/ownership/0

The format that KEDA is searching for is <STORAGE_ACC_NAME>.blob.core.windows.net/<EVENTHUB>/$Default/0

When switching back to Spring Cloud Azure Event Hub Stream Binder 1.2.2 everything works.

I've found this ticket which seems to be related.

Expected Behavior

The Event-Hub Scaler searching for the checkpoint blob in the same place that the Spring Cloud Azure Event Hub Stream Binder creates it.

Actual Behavior

Scaler and Spring Cloud Azure Event Hub Stream Binder are not looking at the same place, resulting in the Scaler not working.

Steps to Reproduce the Problem

1. Deploy a Spring-Cloud-Stream application with Spring Cloud Azure Event Hub Stream Binder version 1.2.3
2. Configure an Event-Hub Scaler

Specifications

• KEDA Version: 1.4.0

  $ kubectl get all -n keda -o=wide
  NAME                                                   READY   STATUS    RESTARTS   AGE   IP             NODE                                NOMINATED NODE   READINESS GATES
  pod/keda-operator-6c6f6fbfdf-q8z8w                     1/1     Running   0          9h    10.240.0.171   aks-additonal-24840637-vmss000002   <none>           <none>
  pod/keda-operator-metrics-apiserver-5bcfc784f4-gq56c   1/1     Running   0          9h    10.240.0.105   aks-additonal-24840637-vmss000000   <none>           <none>
  
  NAME                                      TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)             AGE   SELECTOR
  service/keda-operator-metrics             ClusterIP   10.0.35.58     <none>        8383/TCP,8686/TCP   9h    name=keda-operator
  service/keda-operator-metrics-apiserver   ClusterIP   10.0.224.119   <none>        443/TCP,80/TCP      9h    app=keda-operator-metrics-apiserver
  
  NAME                                              READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS                        IMAGES                                          SELECTOR
  deployment.apps/keda-operator                     1/1     1            1           9h    keda-operator                     docker.io/kedacore/keda:1.4.0                   app=keda-operator
  deployment.apps/keda-operator-metrics-apiserver   1/1     1            1           9h    keda-operator-metrics-apiserver   docker.io/kedacore/keda-metrics-adapter:1.4.0   app=keda-operator-metrics-apiserver
  
  NAME                                                         DESIRED   CURRENT   READY   AGE   CONTAINERS                        IMAGES                                          SELECTOR
  replicaset.apps/keda-operator-6c6f6fbfdf                     1         1         1       9h    keda-operator                     docker.io/kedacore/keda:1.4.0                   app=keda-operator,pod-template-hash=6c6f6fbfdf
  replicaset.apps/keda-operator-metrics-apiserver-5bcfc784f4   1         1         1       9h    keda-operator-metrics-apiserver   docker.io/kedacore/keda-metrics-adapter:1.4.0   app=keda-operator-metrics-apiserver,pod-template-hash=5bcfc784f4
  

• Kubernetes Version: 1.15.10 on AKS

  Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.10", GitCommit:"150f36044fe31bee3891b5a3fae69c17237e022c", GitTreeState:"clean", BuildDate:"2020-02-21T10:02:50Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
  

• Scaler(s): Azure Event Hub Scaler

[stale]

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.

[stale]

This issue has been automatically closed due to inactivity.