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

When there is an invalid pipelinetask name in taskRunSpecs, the cause of the error does not match. #6956

Closed
cugykw opened this issue Jul 21, 2023 · 1 comment · Fixed by #6957
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@cugykw
Copy link
Contributor

cugykw commented Jul 21, 2023

Recently, we planned to upgrade to 0.45.x, tested some new features, etc.,
and found some problems.

When an invalid pipelinetaskname appears in the pipelineName in taskRunSpecs, an error is reported in the status that does not match.

Expected Behavior

The configuration is as follows:

...
  taskRunSpecs:
  - metadata:
      annotations:
        env: prod
    pipelineTaskName: prod-kc
  tasks:
  - name: prod-kc-ea704bf6-54e6-40b0-a957-a73bf2b8f3e5
...

We want to show the appropriate error reason.

Actual Behavior

The actual error is as follows:

  conditions:
  - lastTransitionTime: "2023-07-21T02:06:08Z"
    message: 'PipelineRun cicd/test-kc-inject-annotation doesn''t define taskRunSpecs
      correctly: PipelineRun''s taskrunSpecs defined wrong taskName: "prod-kc", does
      not exist in Pipeline'
    reason: InvalidServiceAccountMappings
    status: "False"
    type: Succeeded

/kind bug

@cugykw cugykw added the kind/bug Categorizes issue or PR as related to a bug. label Jul 21, 2023
@cugykw
Copy link
Contributor Author

cugykw commented Jul 21, 2023

/assign

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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant