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

Fix Wrong Condition Reason When Fails to Stop Sidecars for A Finished TaskRun #5901

Merged
merged 1 commit into from
Dec 20, 2022

Conversation

XinruZhang
Copy link
Member

Changes

This PR fixes a wrong condition reason when fails to stop sidecars for a finished TaskRun.

Prior to this PR, if a TaskRun fails to stop sidecars, the failure reason is TaskRunResolutionFailed which does not make sense at all. This PR creates a new reason TaskRunReasonStopSidecarFailed for StopSideCar failure, and fix the wrong condition reason.

/kind cleanup

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs included if any changes are user facing
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

… TaskRun

Prior to this commit, if a TaskRun fails to stop sidecars, the
failure reason is `TaskRunResolutionFailed` which does not make
sense at all. This commit creates a new reason for StopSideCar
failure, and fix the wrong condition reason.
@tekton-robot tekton-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. release-note-none Denotes a PR that doesnt merit a release note. labels Dec 20, 2022
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 20, 2022
@XinruZhang
Copy link
Member Author

/test pull-tekton-pipeline-integration-tests

Flake: TestExamples/v1beta1/taskruns/dind-sidecar

@abayer
Copy link
Contributor

abayer commented Dec 20, 2022

/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abayer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 20, 2022
@Yongxuanzhang
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 20, 2022
@tekton-robot tekton-robot merged commit 2f69f1e into tektoncd:main Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants