-
Notifications
You must be signed in to change notification settings - Fork 121
Reference example given in pipelines-in-pipelines is not working #785
Comments
@gitcodernitish I wonder if you enabled alpha features in your deployment? |
Got this working , Enabling alpha features was the miss. Thanks @afrittoli . |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
I had the same error using the
|
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close 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. |
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
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"}
Client version: 0.19.1
Pipeline version: v0.27.2
Dashboard version: v0.14.0
The text was updated successfully, but these errors were encountered: