Error in Tutorial Pipeline Run about pipelines-tutorial

[sjbylo]

I had the same error today (25 Sep 2020) with OCP 4.5. I fixed it by using the latest "buildah" task from [0]. After the following steps, the first half of the tutorial should work. I did not try the rest of the tutorial.

Create the latest buildah task:

oc create -f https://raw.githubusercontent.com/tektoncd/catalog/master/task/buildah/0.1/buildah.yaml 

Remove the "ClusterTask" reference in the build-and-deploy pipeline with the "buildah" task:

oc edit pipeline build-and-deploy
...
    - fetch-repository
    taskRef:
      kind: Task    # Replace ClusterTask with Task
      name: buildah
...

[0] https://github.com/tektoncd/catalog/blob/master/task/buildah/0.1/buildah.yaml#L15

[khilmanoj]

Follow the latest doc --> https://docs.openshift.com/container-platform/4.4/pipelines/creating-applications-with-cicd-pipelines.html

[ppitonak]

If you installed OpenShift Pipelines 1.0, follow https://github.com/openshift/pipelines-tutorial/tree/release-tech-preview-1

For Pipelines 1.1 (in preview channel now), follow https://github.com/openshift/pipelines-tutorial/tree/release-tech-preview-2

[atef23]

@ppitonak Thanks, I used the link for Openshift Pipelines 1.0. The first time I ran the pipeline I got this error:

Failed to create build pod "build-and-deploy-run-bkcv7-build-image-qfcc6": pods "build-and-deploy-run-bkcv7-build-image-qfcc6-pod-nzb8d" is forbidden: maximum cpu usage per Pod is 2, but limit is 2500m

The pipeline run succeeded for me after i increased the cpu limits in pipelines-tutorial-core-resource-limits as follows:

kind: LimitRange
apiVersion: v1
metadata:
  name: pipelines-tutorial-core-resource-limits
  namespace: pipelines-tutorial
spec:
  limits:
    - type: Container
      max:
        cpu: '3'
        memory: 6Gi
      default:
        cpu: 500m
        memory: 1536Mi
      defaultRequest:
        cpu: 50m
        memory: 256Mi
    - type: Pod
      max:
        cpu: '3'
        memory: 12Gi

[alif-munim]

I had the same error today (25 Sep 2020) with OCP 4.5. I fixed it by using the latest "buildah" task from [0]. After the following steps, the first half of the tutorial should work. I did not try the rest of the tutorial.

Create the latest buildah task:

oc create -f https://raw.githubusercontent.com/tektoncd/catalog/master/task/buildah/0.1/buildah.yaml 

Remove the "ClusterTask" reference in the build-and-deploy pipeline with the "buildah" task:

oc edit pipeline build-and-deploy
...
    - fetch-repository
    taskRef:
      kind: Task    # Replace ClusterTask with Task
      name: buildah
...

[0] https://github.com/tektoncd/catalog/blob/master/task/buildah/0.1/buildah.yaml#L15

@sjbylo This solution worked for me, thank you!

[ChrystianDuarte]

thanks
@sjbylo sjbylo

Client version: 0.11.0
Pipeline version: v0.11.3
Triggers version: v0.4.0
openshift pipeline operator: 1.0.1
Openshift 4.5

1. Create the latest buildah task:
   oc create -f https://raw.githubusercontent.com/tektoncd/catalog/master/task/buildah/0.1/buildah.yaml
   Remove the "ClusterTask" reference in the build-and-deploy pipeline with the "buildah" task:

oc edit pipeline build-and-deploy ... - fetch-repository taskRef: kind: Task # Replace ClusterTask with Task name: buildah ...
2.correct step 3 (Oficial doc Red Hat openshift 4.5) in parameter deployment-name=vote-ui

tkn pipeline start build-and-deploy -w name=shared-workspace,claimName=source-pvc -p deployment-name=vote-ui -p git-url=http://github.com/openshift-pipelines/vote-ui.git -p IMAGE=image-registry.openshift-image-registry.svc:5000/pipelines-tutorial/vote-ui

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

@openshift-bot: Closing this issue.

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.