Got error sending request to function while doing fission fn test --name kp and page browsing

[qihandeng2]

Dear,
After all steps executed successfully, I got fission fn list below:

**_fission fn list_**
NAME           ENV    EXECUTORTYPE MINSCALE MAXSCALE MINCPU MAXCPU MINMEMORY MAXMEMORY TARGETCPU SECRETS CONFIGMAPS
count          java   newdeploy    1        2        0      0      0         0         80                
data           java   newdeploy    1        2        0      0      0         0         80                
flushcachedata java   newdeploy    1        2        0      0      0         0         80                
fuelavg        java   newdeploy    1        2        0      0      0         0         80                
hello          nodejs poolmgr      0        0        0      0      0         0         0                 
iot-web        python newdeploy    1        1        0      0      0         0         80                
iotstats       java   newdeploy    1        2        0      0      0         0         80                
kc             java   newdeploy    1        10       100m   200m   0         0         70                
kp             java   newdeploy    1        10       100m   200m   0         0         70                
speedavg       java   newdeploy    1        2        0      0      0         0         80 

When I try the last step, fission fn test --name kp, but got the error below:

$ fission fn test --name kp
Warning: The environment variable FISSION_ROUTER is no longer supported for this command
Error: Error calling function kp: 502; Please try again or fix the error: error sending request to function
Error: Error getting function logs from controller: error getting logs from controller, status code: '500'. Try to get logs from log database.
Error: error getting function response

I got the similar error while I am browsing the page http://$FISSION_ROUTER/iot/index.html
And page shows only: error sending request to function.

Looking forward to your help, thank you very much.

[qihandeng2]

The fission dump information attached along.
fission-dump_1591200669.zip

[vishal-biyani]

Hi @qihandeng2 The logs show that KP deployment could not be created. Can you please check function pods are running? Or try re-creating once. Also what is cluster configuration that you are using?

error creating deployment newdeploy-kp-default-95f0-dee6bb561184: failed to create deployment within the timeout window of 120 seconds

[qihandeng2]

Dear @vishal-biyani, thank you.
It seems you are right. I've tried several times, but I always got these output about timeout, when I apply the spec:
`$ fission spec apply
DeployUID: d472e532-0a32-4f03-bf60-5b380a5d7ac8
Resources:

• 9 Functions
• 2 Environments
• 3 Packages
• 1 Http Triggers
• 1 MessageQueue Triggers
• 0 Time Triggers
• 0 Kube Watchers
• 3 ArchiveUploadSpec
  Warning: SpecializationTimeout in function spec.InvokeStrategy.ExecutionStrategy should be a value equal to or greater than 120
  Warning: FunctionTimeout in function spec should be a field which should have a value greater than 0
  Warning: SpecializationTimeout in function spec.InvokeStrategy.ExecutionStrategy should be a value equal to or greater than 120
  Warning: FunctionTimeout in function spec should be a field which should have a value greater than 0
  Warning: SpecializationTimeout in function spec.InvokeStrategy.ExecutionStrategy should be a value equal to or greater than 120
  Warning: FunctionTimeout in function spec should be a field which should have a value greater than 0
  Warning: SpecializationTimeout in function spec.InvokeStrategy.ExecutionStrategy should be a value equal to or greater than 120
  Warning: FunctionTimeout in function spec should be a field which should have a value greater than 0
  Warning: SpecializationTimeout in function spec.InvokeStrategy.ExecutionStrategy should be a value equal to or greater than 120
  Warning: FunctionTimeout in function spec should be a field which should have a value greater than 0
  Warning: SpecializationTimeout in function spec.InvokeStrategy.ExecutionStrategy should be a value equal to or greater than 120
  Warning: FunctionTimeout in function spec should be a field which should have a value greater than 0
  Warning: SpecializationTimeout in function spec.InvokeStrategy.ExecutionStrategy should be a value equal to or greater than 120
  Warning: FunctionTimeout in function spec should be a field which should have a value greater than 0
  Validation Successful
  3 packages created: kc-82d23844-8986-49be-89dc-ac2f44274637, kp-5abfba00-2664-4a27-a9f8-2f69ac20e815, web-pkg
  9 functions created: count, data, fuelavg, iot-web, flushcachedata, iotstats, kc, kp, speedavg
  1 HTTPTrigger created: 6d966491-7ad8-4e42-9efe-6e0d730ed414
  1 MessageQueueTrigger created: kc
  2 environments created: java, python`

BTW, I install the Fission over AWS EKS cluster.
$ kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 23m

And the Kafka and Redis seems running well:
`$ kubectl get all --namespace kafka
NAME READY STATUS RESTARTS AGE
pod/my-cluster-entity-operator-8ddf5fcd4-nkn4j 3/3 Running 0 65s
pod/my-cluster-kafka-0 2/2 Running 0 115s
pod/my-cluster-zookeeper-0 1/1 Running 0 2m47s
pod/strimzi-cluster-operator-6c9d899778-rm6tj 1/1 Running 0 3m15s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/my-cluster-kafka-bootstrap ClusterIP 10.100.178.246 9091/TCP,9092/TCP,9093/TCP 117s
service/my-cluster-kafka-brokers ClusterIP None 9091/TCP,9092/TCP,9093/TCP 117s
service/my-cluster-zookeeper-client ClusterIP 10.100.157.221 2181/TCP 2m49s
service/my-cluster-zookeeper-nodes ClusterIP None 2181/TCP,2888/TCP,3888/TCP 2m49s

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/my-cluster-entity-operator 1/1 1 1 67s
deployment.apps/strimzi-cluster-operator 1/1 1 1 3m17s

NAME DESIRED CURRENT READY AGE
replicaset.apps/my-cluster-entity-operator-8ddf5fcd4 1 1 1 67s
replicaset.apps/strimzi-cluster-operator-6c9d899778 1 1 1 3m17s

NAME READY AGE
statefulset.apps/my-cluster-kafka 1/1 117s
statefulset.apps/my-cluster-zookeeper 1/1 2m49s`

`$ kubectl get all --namespace redis
NAME READY STATUS RESTARTS AGE
pod/redis-single-master-0 1/1 Running 0 88m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/redis-single-headless ClusterIP None 6379/TCP 88m
service/redis-single-master ClusterIP 10.100.100.144 6379/TCP 88m

NAME READY AGE
statefulset.apps/redis-single-master 1/1 88m`

[qihandeng2]

And all the pods and service under namespace fission:

`$ kubectl get all --namespace fission
NAME READY STATUS RESTARTS AGE
pod/buildermgr-6fffcd894d-xhxnf 1/1 Running 0 4m30s
pod/controller-d555cdc5-c9mct 1/1 Running 0 4m31s
pod/executor-d985c68ff-9kcg9 1/1 Running 0 4m31s
pod/fission-prometheus-alertmanager-7669d4498c-85phq 2/2 Running 0 4m31s
pod/fission-prometheus-kube-state-metrics-6d4d9f99bb-z88cg 1/1 Running 0 4m31s
pod/fission-prometheus-node-exporter-rsrcl 1/1 Running 0 4m31s
pod/fission-prometheus-node-exporter-tkm5g 1/1 Running 0 4m31s
pod/fission-prometheus-pushgateway-69996fc598-z8czs 1/1 Running 0 4m31s
pod/fission-prometheus-server-68c57ff55-f86cp 2/2 Running 0 4m31s
pod/influxdb-5ddbc64497-4w8j8 1/1 Running 0 4m30s
pod/kubewatcher-5d4d945f9-lhh2t 1/1 Running 0 4m31s
pod/logger-sf7xl 2/2 Running 0 4m31s
pod/logger-vgm6r 2/2 Running 0 4m31s
pod/mqtrigger-nats-streaming-759f984f56-tsnj6 1/1 Running 3 4m31s
pod/nats-streaming-74584c7d6d-7g7mt 1/1 Running 0 4m31s
pod/router-5d84fdbbb7-sfntc 1/1 Running 0 4m31s
pod/storagesvc-598ffb5956-mt4mj 1/1 Running 0 4m30s
pod/timer-779df7667c-l4hfs 1/1 Running 0 4m31s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/controller ClusterIP 10.100.228.17 80/TCP 4m33s
service/executor ClusterIP 10.100.93.4 80/TCP 4m33s
service/fission-prometheus-alertmanager ClusterIP 10.100.137.188 80/TCP 4m33s
service/fission-prometheus-kube-state-metrics ClusterIP None 80/TCP 4m33s
service/fission-prometheus-node-exporter ClusterIP None 9100/TCP 4m33s
service/fission-prometheus-pushgateway ClusterIP 10.100.237.159 9091/TCP 4m33s
service/fission-prometheus-server ClusterIP 10.100.205.147 80/TCP 4m33s
service/influxdb ClusterIP 10.100.68.234 8086/TCP 4m33s
service/nats-streaming ClusterIP 10.100.174.36 4222/TCP 4m33s
service/router LoadBalancer 10.100.150.51 a0df653d666d3426c9d8a4c5b88514be-785643741.us-east-2.elb.amazonaws.com 80:31334/TCP 4m33s
service/storagesvc ClusterIP 10.100.49.59 80/TCP 4m33s
`