openshift / pipelines-tutorial

A step-by-step tutorial showing OpenShift Pipelines
Apache License 2.0
299 stars 631 forks source link

Build error in step update-ui-image #57

Closed marcoantonioni closed 3 years ago

marcoantonioni commented 4 years ago

Hi all, tested on Openshift CRC 4.2.13

getting this error

web console:

update-ui-image

step-patch Error from server (NotFound): deployments.extensions "ui" not found

command line: .... [build-ui : image-digest-exporter-grtqg] {"level":"warn","ts":1579104550.7637124,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"} [build-ui : image-digest-exporter-grtqg] {"level":"info","ts":1579104550.7639525,"logger":"fallback-logger","caller":"imagedigestexporter/main.go:58","msg":"ImageResource api-image doesn't have an index.json file: stat /builder/home/image-outputs/image/index.json: no such file or directory"}

[apply-ui-manifests : git-source-api-repo-bgr9t] {"level":"warn","ts":1579104566.547371,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"} [apply-ui-manifests : git-source-api-repo-bgr9t] {"level":"info","ts":1579104569.0245762,"logger":"fallback-logger","caller":"git/git.go:103","msg":"Successfully cloned http://github.com/openshift-pipelines/vote-api.git @ master in path /workspace/source"}

[apply-ui-manifests : apply] Applying manifests in k8s directory [apply-ui-manifests : apply] deployment.apps/api configured [apply-ui-manifests : apply] service/api unchanged [apply-ui-manifests : apply] -----------------------------------

[update-ui-image : patch] Error from server (NotFound): deployments.extensions "ui" not found

failed to get logs for task update-ui-image : container step-patch has failed

jorgemoralespou commented 4 years ago

I got the same error and I did apply the deployment manually before running the pipeline and it worked. I'm assuming that the parallelization is not working properly.

We can even see executions like this: image

Which should have never progressed.

christianh814 commented 4 years ago

I ran into this same issue

hupiper commented 4 years ago

I ran into this too. This appears to be an issue with using a secret to access github. see https://github.com/tektoncd/pipeline/issues/1375

whls commented 4 years ago

@hupiper I have the same issue too. but it seems that all repositories are public, Do we also need created a secret for github? And how can I created a secret for github?

whls commented 4 years ago

@marcoantonioni Excuse me, have you finally found the problem?

openshift-bot commented 4 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/57#issuecomment-742955392): >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.