Error: timed out waiting for the condition
Closed this issue · 5 comments
Hi, I tried to deploy my web application using this action.
I got this response after a few minutes.
Hello! Can you paste your logs from that step? A lot could have happened in there, eg. the deployment not getting through because of failing probes, etc. I'm using this GA without any problem in several projects so I'm still not sure if it's the one responsible for this error here.
I am a complete beginner to Kubernetes and helm, also to github actions. I first deployed this web application using the same chart and now tried to automate that.
I only got this log.
Is there any way that I can have more logs?
Also, I have multi cluster contexts in kubeconfig file, if that makes a difference.
Also, I have multi cluster contexts in kubeconfig file, if that makes a difference.
This doesn't, only one context is active at a time. So just make sure the correct context is the one active, otherwise the system will not be able to reach your k8s cluster.
Is there any way that I can have more logs?
Yes, click on this step and it will show a bunch of text logs.
Yes I am sure that the correct cluster is active.
Here are the logs:
Run koslib/helm-eks-action@master
with:
command: helm upgrade nawvel-staging --install --wait ./chart -f ./chart/values-staging.yaml
env:
AWS_REGION: ap-south-1
ECR_REPOSITORY_SERVER: nawvel-server-staging
ECR_REPOSITORY_CLIENT: nawvel-client-staging
AWS_DEFAULT_REGION: ap-south-1
AWS_ACCESS_KEY_ID: ***
AWS_SECRET_ACCESS_KEY: ***
KUBE_CONFIG_DATA: ***
/usr/bin/docker run --name f88420d078f837c7db42d2b31c257e35aefd88_7542ab --label f88420 --workdir /github/workspace --rm -e AWS_REGION -e ECR_REPOSITORY_SERVER -e ECR_REPOSITORY_CLIENT -e AWS_DEFAULT_REGION -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e KUBE_CONFIG_DATA -e INPUT_COMMAND -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e RUNNER_OS -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/Nawvel/Nawvel":"/github/workspace" f88420:d078f837c7db42d2b31c257e35aefd88 "helm upgrade nawvel-staging --install --wait ./chart -f ./chart/values-staging.yaml"
running entrypoint command(s)
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /github/workspace/kubeconfig
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /github/workspace/kubeconfig
Error: timed out waiting for the condition
Alright. Can you check if the deployment is marked as failed in your cluster? The action has executed all steps as expected (its responsibility ends at executing the helm command successfully, which happens in this case).
Since you have the --wait flag, it waits until your new release is successful. I suspect that something goes wrong with the probes or the service startup, that's causing it to timeout.
Closing this issue as the current problem is not related to the action itself.