search

openshift / pipelines-tutorial

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

Unable to trigger pipeline successfully #63

Closed lungss closed 3 years ago

lungss commented 4 years ago

After issuing the command: $ tkn pipeline start build-and-deploy

I'm seeing this in the log:

[build-ui : build] error building at STEP "LABEL "io.openshift.s2i.build.image" "registry.access.redhat.com/rhscl/python-36-rhel7" "io.openshift.s2i.build.source-location" "."": error ensuring container path "/opt/app-root/src": lstat /var/lib/containers/storage/overlay/5e00638bac323dbd1b4584674a5c9047b7ca6a32d63f84a75d4e72cd96e43827/merged/opt: invalid argument

failed to get logs for task build-ui : container step-build has failed  : [{"name":"","digest":"","key":"StartedAt","value":"2020-03-05T07:51:38Z","resourceRef":{}}]

This is what I'm seeing in the task run YAML:

    - container: step-build
      imageID: >-
        quay.io/buildah/stable@sha256:52a993631e5f13f142c1de0ac19ed2188a1a4190bf4530ecaecb23bece0289c3
      name: build
      terminated:
        containerID: >-
          cri-o://e3c259c8d8290069f646c0178b1c3c0c77d1b4dc04a951017abee83f21113d54
        exitCode: 1
        finishedAt: '2020-03-05T07:52:04Z'
        reason: Error
        startedAt: '2020-03-05T07:51:38Z'

Any idea what went wrong here? Thanks in advance!

goern commented 4 years ago

We see a very similar problem:

> oc logs build-minimal-jupyter-hub-image-build-image-lw9bn-pod-5062c0 -c step-build -f
STEP 1: FROM quay.io/thoth-station/s2i-thoth-f31-py37:latest
Getting image source signatures
Copying blob sha256:27366397c7275b2b307c89ddd13f1a583f1c4769e20cf6657d1935be66a6bee4
Copying blob sha256:02f0bf121de1e046f0c7bb5823bb11758e9c09cc051d394a5f9d32639ae317c9
Copying blob sha256:a307ad6614b33d132ff29dedd30f819349b24200c324336cc233e61a224546ae
Copying blob sha256:a31161543ddcd7f82f1b7aa5f60a6053b8f154e34e254d20c89d1e441dcc61d5
Copying blob sha256:53288932acfd950b4cf40a890fcf41996e6588151246a22c1637c0f51cc0e0df
Copying blob sha256:91a84effdc0f55108e7d10ab12ad02b9412b8ad6fe07ca72f8bd47397be22e64
Copying config sha256:d7773c3e4e47b29406d6ddeb7abf1cf3c461cbe6dbf33e0284cc63afcf6c5bed
Writing manifest to image destination
Storing signatures
STEP 2: USER root
error building at STEP "USER root": error ensuring container path "/opt/app-root/src": lstat /var/lib/containers/storage/overlay/24dbb761f7fb79b5f150ae2b761b2c8249878d251e64b5d5b55b47ca105aa2f2/merged/opt: invalid argument

this is Tekton 0.8 on OpenShift 3.11.

IshaniPandey commented 4 years ago

Similar issue faced running a S2I build image. Error: STEP 2: LABEL "io.openshift.s2i.build.image"="nodeshift/ubi8-s2i-web-app:10.x" "io.openshift.s2i.build.source-location"="." error building at STEP "LABEL "io.openshift.s2i.build.image" "nodeshift/ubi8-s2i-web-app:10.x" "io.openshift.s2i.build.source-location" "."": error ensuring container path "/opt/app-root/src": lstat /var/lib/containers/storage/overlay/09ceeddb9a9369dc7d1cec36b7f884f4ebd2336f6945c3ff5d92093a178d51f5/merged/opt: invalid argument STEP-PUSH

Any resolution?

ssalerno-ibmcloud commented 4 years ago

Similar issue, however Tekton 0.9.0 / Pipeline 0.11.3 / OpenShift 4.4 here:

[build-image : git-source-api-repo-69wzc] {"level":"info","ts":1592678972.924522,"caller":"git/git.go:105","msg":"Successfully cloned https://github.com/ssalerno-ibmcloud/vote-api.git @ release-tech-preview-1 in path /workspace/source"}
[build-image : git-source-api-repo-69wzc] {"level":"warn","ts":1592678972.9247334,"caller":"git/git.go:152","msg":"Unexpected error: creating symlink: symlink /tekton/home/.ssh /root/.ssh: file exists"}
[build-image : git-source-api-repo-69wzc] {"level":"info","ts":1592678973.040209,"caller":"git/git.go:133","msg":"Successfully initialized and updated submodules in path /workspace/source"}

[build-image : build] STEP 1: FROM golang:alpine AS builder
[build-image : build] Getting image source signatures
[build-image : build] Copying blob sha256:cbe0275821fc905c0321a44449b7ca670963f2cc0824150bea2125dee8dc7376
[build-image : build] Copying blob sha256:9e0cccf56431698a0981b191f61dcb4ba6afa272d35deb14eaccf2cb46ed0f9d
[build-image : build] Copying blob sha256:a92cc7c5fd73817407fa0e4de5e1fb262a9c0f34c35c7450a2d01a7cef79c62f
[build-image : build] Copying blob sha256:ed8968b2872e472e21554ca58b35a02277634f3e501cc04ab7b0d0963f60f54d
[build-image : build] Copying blob sha256:df20fa9351a15782c64e6dddb2d4a6f50bf6d3688060a34c4014b0d9a752eb4c
[build-image : build] Copying config sha256:3289bf11c2843f3ebc4741a2c08dbb493594ddcd9fb4e4392cd0817d780006b8
[build-image : build] Writing manifest to image destination
[build-image : build] Storing signatures
[build-image : build] STEP 2: WORKDIR /build
[build-image : build] error building at STEP "WORKDIR /build": error ensuring container path "/build": lstat /var/lib/containers/storage/overlay/d33d31a6ae715f84b814024b9e2dad3a1f85a82979d56ba2ef73b1ae5068e248/merged/build: invalid argument

failed to get logs for task build-image : container step-build has failed  : [{"key":"StartedAt","value":"2020-06-20T18:49:33Z","resourceRef":{}}]
SionArtingstall commented 4 years ago

same issue here. Running on OpenShift 4.3 with pipelines operator installed OpenShift-Pipelines: v0.11.3 OpenShift-Pipelines-Triggers: v0.4.0 OpenShift-Pipelines-ClusterTasks: v0.11

STEP-CREATE-DIR-IMAGE-KW2VQ

STEP-GIT-SOURCE-API-REPO-LZJCM

{"level":"info","ts":1597322717.676711,"caller":"git/git.go:105","msg":"Successfully cloned https://github.com/openshift-pipelines/vote-api.git @ master in path /workspace/source"}
{"level":"warn","ts":1597322717.676966,"caller":"git/git.go:152","msg":"Unexpected error: creating symlink: symlink /tekton/home/.ssh /root/.ssh: file exists"}
{"level":"info","ts":1597322717.8005838,"caller":"git/git.go:133","msg":"Successfully initialized and updated submodules in path /workspace/source"}
STEP-BUILD

STEP 1: FROM golang:alpine AS builder
Getting image source signatures
Copying blob sha256:a92cc7c5fd73817407fa0e4de5e1fb262a9c0f34c35c7450a2d01a7cef79c62f
Copying blob sha256:f69a7358283d30e3171b321257500316c7d98b64e87fa1160217fae6f4bb99fc
Copying blob sha256:ed8968b2872e472e21554ca58b35a02277634f3e501cc04ab7b0d0963f60f54d
Copying blob sha256:64e59ab7753c6002a66f633e6eb0dff988f9423964c561ee65dde15a4ebacc7a
Copying blob sha256:df20fa9351a15782c64e6dddb2d4a6f50bf6d3688060a34c4014b0d9a752eb4c
Copying config sha256:1a87ceb1ace58a54c155aec2a5d246f410a9cb01914ae3146d7b2614d11c8057
Writing manifest to image destination
Storing signatures
STEP 2: WORKDIR /build
error building at STEP "WORKDIR /build": error ensuring container path "/build": lstat /var/lib/containers/storage/overlay/2c28baf6f68994c512d63d731eb3ad3cb7bf3511473d653da110b94105f35a12/merged/build: invalid argument
STEP-PUSH

2020/08/13 12:45:40 Skipping step because a previous step failed
STEP-IMAGE-DIGEST-EXPORTER-JB8D7

2020/08/13 12:45:40 Skipping step because a previous step failed
lungss commented 4 years ago

For anyone still facing this issue, this can be resolved by adding '--storage-driver=vfs' to the buildah ClusterTask

If you face similar error at other buildah tasks, add the same parameter as well.

See here for more info: https://github.com/openshift/pipelines-tutorial/issues/66#issuecomment-631163313

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/63#issuecomment-757642932): >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.