Skip to content
This repository has been archived by the owner on Dec 5, 2024. It is now read-only.

Reference example given in pipelines-in-pipelines is not working #785

Closed
nitish-rbrk opened this issue Aug 27, 2021 · 7 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@nitish-rbrk
Copy link

Expected Behavior

pipelinerun-with-pipeline-in-pipeline.yaml should work and able to run the pipeline defined as good-morning-good-afternoon

Actual Behavior

PipelineRun is not able to find the nested pipeline defined in the yaml , The pipeline gets created on the cluster but the PipelineRun refer it in taskref which does not have that task
Error -
it contains Tasks that don't exist: Couldn't retrieve Task "good-morning-good-afternoon": tasks.tekton.dev "good-morning-good-afternoon" not found

Steps to Reproduce the Problem

  1. Install tekton pipeline
  2. Try out example https://github.com/tektoncd/experimental/blob/main/pipelines-in-pipelines/examples/pipelinerun-with-pipeline-in-pipeline.yaml
  3. tkn pr logs

Additional Info

  • Kubernetes version:

    Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:20:00Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}


- Tekton Pipeline version:

**Output of `tkn version` or `kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'`**

Client version: 0.19.1
Pipeline version: v0.27.2
Dashboard version: v0.14.0


<!-- Any other additional information -->
@nitish-rbrk nitish-rbrk added the kind/bug Categorizes issue or PR as related to a bug. label Aug 27, 2021
@nitish-rbrk nitish-rbrk changed the title Example given in pipelines-in-pipelines is not working Reference example given in pipelines-in-pipelines is not working Aug 27, 2021
@afrittoli
Copy link
Member

@gitcodernitish I wonder if you enabled alpha features in your deployment?

@nitish-rbrk
Copy link
Author

Got this working , Enabling alpha features was the miss. Thanks @afrittoli .
Can we add this in the documentation ? I think there can be more user like me who might hit this error.

@afrittoli afrittoli added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 31, 2021
@tekton-robot
Copy link

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.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 29, 2021
@jonashackt
Copy link
Contributor

jonashackt commented Dec 13, 2021

I had the same error using the pipelines-in-pipelines feature. The referenced Tekton docs on Customizing the Pipelines Controller behavior don't really describe how to actually change the feature flag - they just state, that one needs to change a line in the Tekton Pipelines yaml file. If you're asking how to do this "on-the-fly" with kubectl apply I wrote a Q&A on stackoverflow. TLDR; installing the officially released Tekton pipelines yaml and enabling alpha features on-the-fly is possible using a piped combination of curl and sed:

curl https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml | sed "s#stable#alpha#g" | kubectl apply -f -

@tekton-robot
Copy link

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.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 12, 2022
@tekton-robot
Copy link

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
Copy link

@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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants