pipeline
pipeline copied to clipboard
tkn - could not find the requested resource
Running these examples, when getting to:
tkn pipelinerun logs hello-goodbye-run -f -n default
I get this error:
Error: the server could not find the requested resource (get pipelineruns.tekton.dev hello-goodbye-run)
The pipeline is there:
kubectl get pipelinerun -A
NAMESPACE NAME SUCCEEDED REASON STARTTIME COMPLETIONTIME
default hello-goodbye-run True Succeeded 9h
Hi, could you provide more details like your tkn version, Tekton pipeline version? I cannot reproduce this issue.
Thanks.
tkn version
Client version: 2020-04-01T10:57:38Z
Pipeline version: unknown
I dont know how to get the pipeline version
That's a very old tkn
version, you could also try kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
or manually inspect the labels on the controller to find the version.
The instructions for getting the version are provided in the bug report issue template.
@JCzz are you running OpenShift ? (if yes tkn version -n openshift-pipelines
might help). In any case, as @AlanGreene said, this is a very old tkn
version. It might only support "talking to" v1alpha1
API, and you might run a cluster where there is only v1beta1
API for tektoncd/pipeline.
Ideally, you should probably get the latest version of tkn
👼🏼
Thanks Hi @vdemeester
Not running OpenShift, I will try updating tkn
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Hi, Any progress on this ? I'm on a Mac, installed TKN and kubectl
` tkn version Client version: 0.11.0. Pipeline version: v0.48.0 Triggers version: unknown
kubectl version Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:13:27Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"darwin/arm64"} `
Here are the steps followed: ` kubectl apply -f checkout.yaml
kubectl apply -f pipeline_init.yaml
kubectl apply -f pipeline_init_run.yaml
kubectl get pipelines -A
tkn pipeline start pipeline --showlog -p repo-url="myGitRepo" `
Hi @max3ndeavour, it looks like you're running a very old version of the Tekton CLI:
Client version: 0.11.0.
That was released in July 2020, almost 3 years ago.
The latest release is v0.31.0, can you try upgrading and testing again?
Thank you for the feedback. Indeed, I installed through this page that leads to an old version. Using the brew install is way better ;)
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
with a justification.
Mark the issue as fresh with /remove-lifecycle rotten
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen
with a justification. Mark the issue as fresh with/remove-lifecycle rotten
with a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozen
with a justification./close
Send feedback to tektoncd/plumbing.
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.