Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aicoe-ci fails with CouldntGetTask #134

Closed
pacospace opened this issue Aug 24, 2021 · 6 comments
Closed

aicoe-ci fails with CouldntGetTask #134

pacospace opened this issue Aug 24, 2021 · 6 comments
Assignees
Labels
human_intervention_required kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@pacospace
Copy link

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
Copy link
Author

pacospace commented Aug 24, 2021

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 pacospace added kind/bug Categorizes issue or PR as related to a bug. human_intervention_required priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Aug 24, 2021
@pacospace pacospace changed the title aicoe-ci fails when using /deploy aicoe-ci fails with CouldntGetTask Aug 24, 2021
@pacospace
Copy link
Author

Related: tektoncd/pipeline#2013

@sesheta
Copy link
Contributor

sesheta commented Nov 22, 2021

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 sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 22, 2021
@sesheta
Copy link
Contributor

sesheta commented Dec 22, 2021

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 sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 22, 2021
@sesheta
Copy link
Contributor

sesheta commented Jan 21, 2022

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

/close

@sesheta sesheta closed this as completed Jan 21, 2022
@sesheta
Copy link
Contributor

sesheta commented Jan 21, 2022

@sesheta: Closing this issue.

In response to this:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
human_intervention_required kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

3 participants