-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to find any running pod for hello. Retrying.. #85
Comments
Did you install kubeless itself in your k8s cluster ? |
yes, i did. |
Can you tell us a which version of kubeless and which version of k8s you are running ? Also if you deploy a function with |
hi @rushins there are two options here: either the function is deployed but the client is not able to find it (which can be similar to #77) or the function failed to be deployed. If you can see the pod when running |
my kubless version: 0.0.20 i follow the steps$ kubectl version $ npm install serverless -g Clone this repo and check the example function $ git clone https://github.com/serverless/serverless-kubeless provider: plugins:
functions: $ npm installi get this error while deploying (serverless deploy) ======================================= Error: Unable to retrieve the status of the hello deployment
|
@rushins Probably something went wrong with the deployment. Do you have RBAC enabled in your cluster? Can you send us the output of executing |
yes, its RBAC enabled in cluster. i get this output from the command you requested. (kubectl logs -n kubeless $(kubectl get pods -n kubeless -l kubeless=controller -o=name) 1 reflector.go:201] github.com/kubeless/kubeless/pkg/controller/controller.go:118: Failed to list *spec.Function: User "system:serviceaccount:kubeless:controller-acct" cannot list functions.k8s.io at the cluster scope. (get functions.k8s.io) |
If that is the case you need to deploy the RBAC version of kubeless:
|
ok i tried but it has all old ones which i wasnt able to remove. Error from server (AlreadyExists): error when creating "https://github.com/kubeless/kubeless/releases/download/v0.2.4/kubeless-rbac-v0.2.4.yaml": statefulsets.apps "kafka" already exists |
i tried to clean up and deleted majority of the old ones like deployments, services, pods but i wasn't able to delete the pod "zoo-0" . |
Sorry, you can clean up the installation using |
@andresmgot : i did cleanup and tried. this time worked nice but one particular thing is still not working (sererless logs -f hello). here are my ouptuts. kubectl get function $ serverless invoke -f hello -l
|
Hi @rushins, indeed that's a bug on our side. The command is finding a pod (that is not relevant to serverless) and since it doesn't have labels it causes the crash. The above PR should fix it. |
The fix is now landed, @rushins can you try with the master version of the plugin and check if it fix your issue? |
i will try and let you know . |
hi @andresmgot : no change i still see the error while running the logs command serverless logs -f hello TypeError: Cannot read property 'function' of undefined |
hi @rushins, it seems that you are still using the old code (serverless-kubeless/lib/get-logs.js:101 is not Let me release a new patch version, that will make it easier to see the changes. |
you should be able to see the fix with the latest version 0.2.4 |
same error here
when try deploy again:
|
hi @gabrielmancini, can you send the logs of the controller? You can retrieve them executing:
|
I had the same issue and I was using v0.3.2 for kubeless. So I checked if there was a new version for that and I found 0.3.3 And I updated |
@ryuheechul Thanks for your confirmation. Yes v0.3.2 was sent out with a backward incompatibility issue (we apologize for that) and v0.3.3 fixed that. This serverless plugin was tested with v0.3.3 so anyone got trouble with v0.3.2 please consider to upgrade |
@ngtuna You are very welcome! |
using kubeless v0.3.3 serverless -v now on linux, when deploy
when try deploy again
the log u ask
versions
|
@gabrielmancini thank you for the logs. It seems that the function gets successfully created:
but the client is not able to retrieve the deployment information. Does the deployment/pod gets created? To try to reproduce it, in which platform are you running Kubernetes? Does it have RBAC enabled? |
cat serverless.yml
cat handler.js
cat package.json
|
@gabrielmancini those files seem correct, does If that is the case, the issue about the client not able to retrieve the function could be caused due to a bad synchronization between the client clock and the Kubernetes cluster. When you deploy a function and then you execute |
If there are bad values in the |
hi @ianserlin, I have just released the version v0.4.2 for fixing that issue. Could you check if it is now resolved? |
I can confirm this now converts to string and does not cause an issue, I'll close the PR in the serverless repo. Thanks @andresmgot! |
hi @rushins I've just encountered the same issue as you
|
Just deleted the old namespace completely and reinstall as stated “kubectl delete ns kubeless” first and create again “kubectl create ns kubeless” and install . |
i got this error "Unable to find any running pod for hello. Retrying.." while doing serverless deploy ? i have cloned all the files and i have kubernetes cluster running on-premise ? what i am missing here
The text was updated successfully, but these errors were encountered: