RabbitMQ Trigger doesn't work after upgrading to 2.2

[basilfx]

I've updated from KEDA Chart 2.0.1 to 2.2.1, and I noticed that scaling doesn't work anymore (by observing the keda user in the RabbitMQ connection list in the management interface). When I downgrade back to 2.0.1, it works again. I'm running K8s 1.19.

I have the following ScaledObject (I also updated the parameters with 2.2 parameters, no effect):

apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: redacted
  namespace: redacted
spec:
  maxReplicaCount: 10
  minReplicaCount: 1
  scaleTargetRef:
    name: redacted
  triggers:
  - metadata:
      host: amqp://keda:[email protected]
      queueName: Gateway-Queue
      queueLength: "100"
    type: rabbitmq

KEDA seems to pick-up the job, and reports the following (but note ScalerNotActive):

...
status:
  conditions:
  - message: ScaledObject is defined correctly and is ready for scaling
    reason: ScaledObjectReady
    status: "True"
    type: Ready
  - message: Scaling is not performed because triggers are not active
    reason: ScalerNotActive
    status: "False"
    type: Active
  externalMetricNames:
  - rabbitmq-Gateway-Queue
  originalReplicaCount: 1
  scaleTargetGVKR:
    group: apps
    kind: Deployment
    resource: deployments
    version: v1
  scaleTargetKind: apps/v1.Deployment

According to the release notes, there are no breaking changes. But I don't understand why it isn't working, or how I should activate the trigger.

Any idea's?

[tomkerkhove]

This typically means that the queue is empty and there is no work to scale, hence the trigger is not active.

Does that match your queue depth or not?

[basilfx]

I can confirm that scaling still works.

I got confused by the behavior of 2.0 versus 2.2. In the old version, I had an active connection for a KEDA user (as configured) in the connections overview in the management interface of RabbitMQ (screenshot below, of 2.2 behavior). I guess that has changed now, and together with 'ScalerNotActive' I concluded that something was wrong.