kedacore container keeps crashing

[ameetkonnur]

I was trying the Azure Functions with Azure Storage Queue trigger. Since the Functions wasnt getting triggered when i looked at my pods in "keda" namespace on my AKS cluster i see the below error. I guess this is the reason why it isnt working. Any pointers on solving this ?

NAME READY STATUS RESTARTS AGE
keda-cdc47687c-9rrsj 0/1 CrashLoopBackOff 5 3m42s
osiris-osiris-edge-activator-8656c567c9-nsmth 1/1 Running 0 3m40s
osiris-osiris-edge-endpoints-controller-cd68bcb65-mnfdf 1/1 Running 0 3m40s
osiris-osiris-edge-endpoints-hijacker-86d74b6fd7-qd6z9 1/1 Running 0 3m39s
osiris-osiris-edge-proxy-injector-85f87d89d4-phmks 1/1 Running 0 3m39s
osiris-osiris-edge-zeroscaler-6576cdd5bd-wt8v7 1/1 Running 0 3m39s

[ursathi]

We are also facing the same issue. Here is the describe output

Name: keda-59748d7c48-mxbj7
Namespace: keda1
Priority: 0
PriorityClassName:
Node: aks-nodepool1-38845997-vmss000000/10.240.0.4
Start Time: Tue, 28 Jan 2020 11:13:58 +0530
Labels: instance=keda-instance
name=keda
pod-template-hash=59748d7c48
Annotations:
Status: Running
IP: 10.240.0.87
Controlled By: ReplicaSet/keda-59748d7c48
Containers:
keda:
Container ID: docker://101b55443ced3a72bfd73ab412b529fc9987f9ed4c744ad802faf35cd01685dc
Image: kedacore/keda:latest
Image ID: docker-pullable://kedacore/keda@sha256:142d7e55e99a47df38f4ecb5b4c63943184855cd3172258531138aad05d2c410
Ports: 6443/TCP, 8080/TCP
Host Ports: 0/TCP, 0/TCP
Args:
--log-level=info
/adapter
--secure-port=6443
--logtostderr=false
--v=2
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 2
Started: Tue, 28 Jan 2020 11:15:02 +0530
Finished: Tue, 28 Jan 2020 11:15:02 +0530
Ready: False
Restart Count: 3
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from keda-token-dtm82 (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
keda-token-dtm82:
Type: Secret (a volume populated by a Secret)
SecretName: keda-token-dtm82
Optional: false
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message

---

Normal Scheduled 87s default-scheduler Successfully assigned keda1/keda-59748d7c48-mxbj7 to aks-nodepool1-38845997-vmss000000
Normal Pulling 24s (x4 over 86s) kubelet, aks-nodepool1-38845997-vmss000000 Pulling image "kedacore/keda:latest"
Normal Pulled 23s (x4 over 76s) kubelet, aks-nodepool1-38845997-vmss000000 Successfully pulled image "kedacore/keda:latest"
Normal Created 22s (x4 over 75s) kubelet, aks-nodepool1-38845997-vmss000000 Created container keda
Normal Started 22s (x4 over 75s) kubelet, aks-nodepool1-38845997-vmss000000 Started container keda
Warning BackOff 7s (x7 over 65s) kubelet, aks-nodepool1-38845997-vmss000000 Back-off restarting failed container

Here is the kubectl version details

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.8", GitCommit:"211047e9a1922595eaa3a1127ed365e9299a6c23", GitTreeState:"clean", BuildDate:"2019-10-15T12:11:03Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.8", GitCommit:"1da9875156ba0ad48e7d09a5d00e41489507f592", GitTreeState:"clean", BuildDate:"2019-11-14T05:19:20Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

And, even after deploying our app container, hpa is not getting created

Any help will be highly appreciated

[jeffhollan]

Sorry I missed this. Yes there was a change in deployment args with the recent KEDA 1.1 release that required a change in the Azure Functions core tools. The change is in but hasn’t rolled out yet globally. For now the best bet is to not install keda with func install Kubernetes but rather helm or yaml as described at keda.sh

[ursathi]

Thanks @jeffhollan