-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Tekton, Internal error occurred: context deadline exceeded #2877
Comments
/kind question @Mage-Sky thanks for the issue. It seems like there is a network issue on your cluster somehow (between the k8s api-server and the webhook). Can you share more detail on your setup ? (kubernetes version ? OpenShift ? Running "services" (like knative, … ) ?) |
Thank you for your reply. [root@master ~]# kubectl version Don't have too many services in this kubernetes. NAMESPACE NAME READY STATUS I guess it is the problem about network, but how can I check it? |
It seems there is something wrong with
|
Thank you very much. Maybe I will solve the issue about flannel at first. |
After all pods run well, the error was [root@master tekton]# kubectl apply -f hello-world.yaml |
About the flannel status, ● flanneld.service - Flanneld overlay address etcd agent Jul 03 13:28:59 master flanneld-start[9706]: E0703 13:28:59.453387 9706 network.go:102] failed to retrieve network config: client: etcd cluster is unavailable or misconfigured; error #0: EOF |
[root@master ~]# kubectl get all -n tekton-pipelines NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME READY UP-TO-DATE AVAILABLE AGE NAME DESIRED CURRENT READY AGE |
edit
it works for me. |
Thanks @JianleiZhang ! @Mage-Sky let us know if this helps. It appears there's some problem with using Tekton and flannel, at least this other issue also hit similar problems using flannel for network: #2831 |
Thank you for your help, but it still has error for me. Error from server (InternalError): error when creating "task-hello-world.yaml": Internal error occurred: failed calling webhook "webhook.pipeline.tekton.dev": Post https://tekton-pipelines-webhook.tekton-pipelines.svc:443/defaulting?timeout=30s: no endpoints available for service "tekton-pipelines-webhook" |
The error may be not about flannel. 'Issues like this are ultimately caused by a mismatch between the webhook's service name configured on the CRD resources (which are not templated as part of the Helm chart, and thus are not updated automatically if the release name is set to something other than cert-manager or if the namespace is also not cert-manager).' |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Is it possible to re-open this issue please? I have also experienced this issue, but I am running on GKE cluster on Shared VPC. I also notice the service is trying to resolve DNS to Steps to reproduce:
base/kustomization.yaml
base/task.yaml
Here is the version I am running:
Here are the resources running in
|
/reopen |
@c5haw: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Expected Behavior
Actual Behavior
[root@master tekton]# kubectl apply -f taskrun1.yaml
Error from server (InternalError): error when creating "taskrun1.yaml": Internal error occurred: failed calling webhook "webhook.pipeline.tekton.dev": Post https://tekton-pipelines-webhook.tekton-pipelines.svc:443/defaulting?timeout=30s: context deadline exceeded
Steps to Reproduce the Problem
[root@master tekton]# cat taskrun1.yaml
apiVersion: tekton.dev/v1alpha1
kind: TaskRun
metadata:
name: run-with-parameters
spec:
taskRef:
name: task-with-parameters
inputs:
params:
- name: flags
value: "--set"
- name: someURL
value: "https://github.com/knative-sample"
Additional Info
tekton-pipelines tekton-dashboard-584fc79989-rxv5b 1/1 Running 4 20h
tekton-pipelines tekton-pipelines-controller-85496b94dd-tmnk5 1/1 Running 0 20h
tekton-pipelines tekton-pipelines-webhook-7cd58cd7cb-t569j 1/1 Running 0 20h
The text was updated successfully, but these errors were encountered: