search

AICoE / aicoe-ci

AICoE-CI using TektonCD pipelines and triggers
13 stars 13 forks source link

aicoe-ci fails with CouldntGetTask #134

Closed pacospace closed 2 years ago

pacospace commented 3 years ago

Describe the bug aicoe-ci fails when using /deploy

To Reproduce Steps to reproduce the behavior:

  1. Open PR is s2i-miniaml-notebook
  2. Use /deploy

Expected behavior Pipeline finishes successfully

Screenshots

completionTime: '2021-08-24T08:23:38Z'
conditions:
  - lastTransitionTime: '2021-08-24T08:23:38Z'
    message: >-
      failed to create task run pod
      "aicoe-pipelinerun-925459be-f41d-474e-acff-461b1078162e-r--f55wp": Pod
      "aicoe-pipelinerun-925459be-f41d-474e-acff-461b1078162e-r--lhrsk" is
      invalid: [spec.volumes[16].secret.secretName: Required value,
      spec.containers[6].volumeMounts[1].name: Not found: "quay-creds"]. Maybe
      missing or invalid Task opf-ci-pipelines/pr-build-release
    reason: CouldntGetTask
    status: 'False'
    type: Succeeded
podName: ''

Additional context Add any other context about the problem here.

pacospace commented 3 years ago

Looking at previous steps which I expected to fail, it seems there is another issue causing this:

in gather-info

2021/08/24 08:33:46 warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied
+ [[ ! -f .aicoe-ci.yaml ]]
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''
+ echo -n ''

in query-config

2021/08/24 08:33:47 warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied
done

from check-results

2021/08/24 08:33:49 warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied
+ ls -la /tekton/results/
total 4
drwxrwxrwx. 2 root    root 4096 Aug 24 08:33 .
drwxr-xr-x. 8 root    root  114 Aug 24 08:33 ..
-rw-r--r--. 1 default root    0 Aug 24 08:33 base-image
-rw-r--r--. 1 default root    0 Aug 24 08:33 build-source-script
-rw-r--r--. 1 default root    0 Aug 24 08:33 build-stratergy
-rw-r--r--. 1 default root    0 Aug 24 08:33 deploy-image-name
-rw-r--r--. 1 default root    0 Aug 24 08:33 deploy-project-name
-rw-r--r--. 1 default root    0 Aug 24 08:33 deploy-project-org
-rw-r--r--. 1 default root    0 Aug 24 08:33 dockerfile-path
-rw-r--r--. 1 default root    0 Aug 24 08:33 overlay-contextpath
-rw-r--r--. 1 default root    0 Aug 24 08:33 pytest-env
-rw-r--r--. 1 default root    0 Aug 24 08:33 registry
-rw-r--r--. 1 default root    0 Aug 24 08:33 registry-org
-rw-r--r--. 1 default root    0 Aug 24 08:33 registry-project
-rw-r--r--. 1 default root    0 Aug 24 08:33 registry-secret
pacospace commented 3 years ago

Related: https://github.com/tektoncd/pipeline/issues/2013

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/AICoE/aicoe-ci/issues/134#issuecomment-1018606804): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/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.