Keda: Cron Scaler throws error - unknown timezone

Created on 13 Jul 2020  路  7Comments  路  Source: kedacore/keda

Expected Behavior

That this configuration works as described in the docs. But every time I am receiving an error in the log, that the timezone is unknown.

apiVersion: keda.k8s.io/v1alpha1
kind: ScaledObject
metadata:
  name: test
spec:
  scaleTargetRef:
    deploymentName: test
  minReplicaCount: 1
  maxReplicaCount: 2
  triggers:
    - type: cron
      metadata:
        timezone: Europe/Berlin
        start: 00 15 * * *
        end: 30 15 * * *
        desiredReplicas: "2"

Actual Behavior

E0713 11:41:25.133260       1 provider.go:94] keda_metrics_adapter/provider "msg"="error getting metric for scaler" "error"="Unable to load timezone. Error: unknown time zone Europe/Berlin"  "ScaledObject.Name"="test" "ScaledObject.Namespace"="test" "Scaler"={}

Steps to Reproduce the Problem

  1. Deploy KEDA 1.5.0
  2. Create ScaledObject from type cron with the configuration above
  3. Get logs from keda-operator-metrics-apiserver to check for any errors

Specifications

  • KEDA Version: 1.5.0
  • Platform & Version: Azure Kubernetes Service
  • Kubernetes Version: 1.16.10
  • Scaler(s): cron

Working configuration with KEDA 1.5.0 and Cron Scaler

apiVersion: keda.k8s.io/v1alpha1
kind: ScaledObject
metadata:
  name: test
spec:
  scaleTargetRef:
    deploymentName: test
  minReplicaCount: 1
  maxReplicaCount: 2
  triggers:
    - type: cron
      metadata:
        timezone: Local
        start: 00 15 * * *
        end: 30 15 * * *
        desiredReplicas: "2"
bug

Most helpful comment

Glad you've noticed that @zroubalik is a machine that we are scaling out with KEDA, but don't tell anyone!

All 7 comments

@ckuduvalli FYI, would be great if we have e2e tests for Cron scaler.

@dan-leanix thanks for reporting this. We have a flaw in our release/build process, which resulted in incorrect KEDA docker images (they were lacking data needed for Cron scaler). We have rebuild the images, so they should be ok now.

Could you please redeploy KEDA (or refetch images for KEDA Operator and Metrics Adapter) and give a try once again?

Thanks a lot!

@zroubalik Damn that was fast. 馃憤

Sure, I will give it a try and let you know how it goes.

@zroubalik I am confirming the issue is solved with the rebuilt images!

Thanks again for the blazing fast response. I am closing the issue.

Glad you've noticed that @zroubalik is a machine that we are scaling out with KEDA, but don't tell anyone!

@ckuduvalli FYI, would be great if we have e2e tests for Cron scaler.

Sure will try to add them. Will sync up with you.

Created #935 for this

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jeffhollan picture jeffhollan  路  3Comments

sebastianspross picture sebastianspross  路  3Comments

slayer picture slayer  路  4Comments

aman-bansal picture aman-bansal  路  4Comments

genadyk picture genadyk  路  3Comments