You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kubernetes platform (e.g. Google Kubernetes Engine)
Amazon EKS
Describe the bug
The packages are getting stuck in the running state, and there are no logs available for the packages.
I tried below things:
I attempted to create a package out of a simple .py file, but it also became stuck in a running state.
I tried deleting everything, including the environment, routes, and all packages, and then created a new package, but the issue persists.
The fission check shows everything is functioning correctly, and all pods are operational.
I verified the AWS keys in the deployment configuration as well. I checked the logs of the executor and StorageSVC pod, but there are no error logs available to debug this issue. [Using S3 as storage]
Tried rollout restarting the whole fission deployments.
Fission/Kubernetes version
v1.29
Kubernetes platform (e.g. Google Kubernetes Engine)
Amazon EKS
Describe the bug
The packages are getting stuck in the running state, and there are no logs available for the packages.
I tried below things:
To Reproduce
fission pkg create --sourcearchive new-test.zip --env nodejs --name node-sample-test
Expected result
NAME BUILD_STATUS ENV LASTUPDATEDAT NAMESPACE
node-sample-test succeeded nodejs 03 Apr 24 12:44 IST default
Actual result
NAME BUILD_STATUS ENV LASTUPDATEDAT NAMESPACE
node-sample-test running nodejs 03 Apr 24 12:44 IST default
Screenshots/Dump file
fission-dump_1712129393.zip
Additional context
fission pkg info --name function-name doesn't show any logs while it is running state, it will only show the logs if the pkg is failed or succeeded.
The text was updated successfully, but these errors were encountered: