Closed Waqas-Shah-42 closed 1 week ago
In my opinion this should be labelled as bug.
@Waqas-Shah-42 Please use default
namespace while creating fission resources. You have used release namespace fission
.
fission env create --name nodejs --image fission/node-env --namespace default
curl https://raw.githubusercontent.com/fission/examples/master/nodejs/hello.js > hello.js
fission function create --name hello --env nodejs --code hello.js --namespace default
fission function test --name hello --namespace default
Fission/Kubernetes version fission: v1.20.2 (also tried with v1.20.1) kubernetes version: v1.29.4-eks-036c24b
Kubernetes platform (e.g. Google Kubernetes Engine) EKS
Describe the bug I installed fission using helm chart with routerServiceType of type ClusterIP using the following command
helm install --version v1.20.2 --namespace fission fission \ --set routerServiceType=ClusterIP \ fission-charts/fission-all
Then I followed the example given after the helm installation which were as following (with namespace updated):-
All the above commands ran successfully. However the following command failed
It gave the following output
Error: calling function hello: 404; Please try again or fix the error: 404 page not found Error: getting function logs: no active pods found for function in namespace fission. Try to get logs from log database.
When I enter fission fn list it shows the function is deployed
To Reproduce
Expected result The function to run as expected.
Actual result The function does not run at all.
Screenshots/Dump file
Additional context The helm installation was done with routerServiceType of type ClusterIP using helm chart