We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
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.
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
The text was updated successfully, but these errors were encountered:
/assign
Sorry, something went wrong.
cugykw
Successfully merging a pull request may close this issue.
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:
We want to show the appropriate error reason.
Actual Behavior
The actual error is as follows:
/kind bug
The text was updated successfully, but these errors were encountered: