Error from server (MethodNotAllowed) while running oc appy -f triggers template

[soukainakhalkhouli]

Hello team,

I'm getting this error while running oc appy -f triggers template i'm using tekton client below version :

oc apply -f build-and-deploy-openshift-triggers.yaml triggertemplate.triggers.tekton.dev/catapp-build-and-deploy unchanged triggerbinding.triggers.tekton.dev/catapp-build-and-deploy unchanged serviceaccount/catapp unchanged role.rbac.authorization.k8s.io/catapp unchanged rolebinding.rbac.authorization.k8s.io/catapp unchanged route.route.openshift.io/el-catapp unchanged Error from server (MethodNotAllowed): error when creating "build-and-deploy-openshift-triggers.yaml": create not allowed while custom resource definition is terminating

Client version: 0.23.1 Pipeline version: v0.34.1 Triggers version: v0.19.1

Trigger template code : apiVersion: triggers.tekton.dev/v1alpha1 kind: TriggerTemplate metadata: name: catapp-build-and-deploy spec: params:

• name: URL description: The repository url to build and deploy.
• name: REVISION description: The revision to build and deploy.
• name: NAMESPACE description: The namespace is used by OpenShift's internal image registry to store the built image.
• name: DEPLOYMENT description: Name of the Deployment and the container name in the Deployment.
• name: SERVICE_ACCOUNT description: The ServiceAccount under which to run the Pipeline. resourcetemplates:
• apiVersion: tekton.dev/v1beta1 kind: PipelineRun metadata: generateName: catapp-build-and-deploy- spec: serviceAccountName: $(params.SERVICE_ACCOUNT) pipelineRef: name: build-and-deploy-openshift resources:
  • name: source resourceSpec: type: git params:
    • name: revision value: $(params.REVISION)
    • name: url value: $(params.URL)
  • name: image resourceSpec: type: image params:
    • name: url value: image-registry.openshift-image-registry.svc:5000/$(params.NAMESPACE)/catapp:$(params.REVISION) params:

  • name: DEPLOYMENT value: $(params.DEPLOYMENT)

    apiVersion: triggers.tekton.dev/v1alpha1 kind: TriggerBinding metadata: name: catapp-build-and-deploy spec: params:

• name: URL value: $(body.repository.clone_url)
• name: REVISION value: $(body.pull_request.head.sha)
• name: NAMESPACE value: catapp
• name: DEPLOYMENT value: catapp

• name: SERVICE_ACCOUNT value: pipeline

  apiVersion: v1 kind: ServiceAccount metadata: name: catapp

  kind: Role apiVersion: rbac.authorization.k8s.io/v1 metadata: name: catapp rules:

  Permissions for every EventListener deployment to function

  • apiGroups: ["triggers.tekton.dev"] resources: ["eventlisteners", "triggerbindings", "triggertemplates"] verbs: ["get"]
  • apiGroups: [""] resources: ["configmaps"] verbs: ["get", "list", "watch"]

    Permissions to create resources in associated TriggerTemplates

  • apiGroups: ["tekton.dev"] resources: ["pipelineruns"] verbs: ["create"]

    apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: catapp subjects:

  • kind: ServiceAccount name: catapp roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: catapp

    apiVersion: triggers.tekton.dev/v1alpha1 kind: EventListener metadata: name: catapp spec: serviceAccountName: catapp triggers:

• name: pullrequest-build-and-deploy template: name: catapp-build-and-deploy bindings:

  • name: catapp-build-and-deploy

    apiVersion: route.openshift.io/v1 kind: Route metadata: labels: eventlistener: catapp name: el-catapp spec: port: targetPort: http-listener to: kind: Service name: el-catapp

[openshift-bot]

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]

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]

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[bot]]

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/pipelines-tutorial/issues/157#issuecomment-1237534264): >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.