search

openshift / pipelines-tutorial

A step-by-step tutorial showing OpenShift Pipelines
Apache License 2.0
298 stars 621 forks source link

Error creating resources and running demo #82

Closed Keyvan-rh closed 3 years ago

Keyvan-rh commented 4 years ago

Using OCP 4.4.3 When running the tutorial, I'm getting this error in v0.10.7: oc create -f 04_pipeline.yaml

error: unable to recognize "04_pipeline.yaml": no matches for kind "Pipeline" in version "tekton.dev/v1beta1"

the reason is the version of the API is v1beta1 but the operator is using/expecting v1alpha1 in the other hand if i do the same for the apply-mainfests it would error :

Error from server (BadRequest): error when creating "01_apply_manifest_task.yaml": admission webhook "webhook.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "params"

this time is because the schema has changed between alpha and beta. please make sure all yamls are using the same version and running with latest Pipline operator (at the moment is v0.10.7)

josequaresma commented 4 years ago

I get similar error on OCP 4.3.0 and pipelines 0.10.7: error: unable to recognize "01_pipeline/01_apply_manifest_task.yaml": no matches for kind "Task" in version "tekton.dev/v1beta1"

DonSchenck commented 4 years ago

I'm getting this as well.

piyush-garg commented 4 years ago

If you want to use the operator v0.10.7 then please use release-0.9 branch of the tutorial or if you want to use current master or release-tech-preview-1 of tutorial then please use operator 0.11.x

Keyvan-rh commented 4 years ago

Is it possible to use the 1.0.1 which is RedHat GAed and not the community one?

piyush-garg commented 4 years ago

@Keyvan-rh Yaa you can use that one also, it has v1beta1 resources.

tux1980 commented 3 years ago

Hi, I'm getting this either: error: unable to recognize "03_trigger.yaml": no matches for kind "Trigger" in version "triggers.tekton.dev/v1alpha1"

openshift-bot commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/pipelines-tutorial/issues/82#issuecomment-790628451): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.