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

Taskruns when kicked off from dashboard doesn't account for workspace input like it does for params #2105

Closed
hakuna-matatah opened this issue Jun 25, 2021 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@hakuna-matatah
Copy link

hakuna-matatah commented Jun 25, 2021

Describe the bug

Taskruns when kicked off from dashboard doesn't account for workspace input like it does for params

Taskruns that contains workspaces input in it's definition will fail with "Validation failure" because we cannot give any input for taskruns that have workspaces enabled from dashboard. It gives following message:

TaskRunValidationFailed
declared workspace "xxxxx" is required but has not been bound

Expected behaviour

Taskruns should allow input for workspaces name like it takes input for params.

Steps to reproduce the bug

Create a task with workspace config and kick off a taskrun for that task from dashboard and it will fail.

Environment details

  • Kubernetes Platform:
  • Kubernetes or OpenShift version:
  • Install mode (if on OpenShift):
  • Cloud-provider/provisioner:
EKS
  • Versions:
    • Tekton Dashboard:
    • Tekton Pipelines:
    • Tekton Triggers:
  • Install namespaces:
    • Tekton Dashboard:
      - gcr.io/tekton-releases/github.com/tektoncd/dashboard/cmd/dashboard@sha256:b1519c53577d02d7452bfff39f5c25fa6fd64bee3f1716f00ddfb8c2c65a6fd1
    • Tekton Pipelines:
    • Tekton Triggers:

Additional Info

@hakuna-matatah hakuna-matatah added the kind/bug Categorizes issue or PR as related to a bug. label Jun 25, 2021
@AlanGreene
Copy link
Member

Thanks for the issue @hakuna-matatah, we're already tracking this in #1283. Closing as a duplicate.

@AlanGreene AlanGreene added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Jun 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

2 participants