[go: nahoru, domu]

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

[release-1.2] Fix RerunOnFailure RunStrategy #11972

Merged

Conversation

fossedihelm
Copy link
Contributor

What this PR does

This is a manual cherry-pick of #11963

Fixes #

Why we need it and why it was done in this way

The following tradeoffs were made:

The following alternatives were considered:

Links to places where the discussion took place:

Special notes for your reviewer

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note

Fix RerunOnFailure RunStrategy

/cc @acardace

Simplify function by returning early on error.

Signed-off-by: Antonio Cardace <acardace@redhat.com>

(cherry picked from commit 6b96bee)
Signed-off-by: fossedihelm <ffossemo@redhat.com>
Keep track of the last used RunStrategy to correctly process
the `RerunOnFailure` RunStrategy.

Before this patch the usage of this API was actually broken.

Signed-off-by: Antonio Cardace <acardace@redhat.com>

(cherry picked from commit 2645368)
Signed-off-by: fossedihelm <ffossemo@redhat.com>
The name is misleading as it returns true if all expectations have
been satisfied and the controller does not need to sync.

Signed-off-by: Antonio Cardace <acardace@redhat.com>
(cherry picked from commit 62780b6)
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API size/L labels May 24, 2024
@fossedihelm fossedihelm changed the title Release 1.2 fix run strategy [release-1.2] Fix RerunOnFailure RunStrategy May 24, 2024
@acardace
Copy link
Member

/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: acardace

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 24, 2024
@kubevirt-bot
Copy link
Contributor
kubevirt-bot commented May 24, 2024

@fossedihelm: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubevirt-goveralls 53048eb link false /test pull-kubevirt-goveralls-1.2

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-sigs/prow repository. I understand the commands that are listed here.

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label May 24, 2024
@kubevirt-commenter-bot
Copy link

/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

@kubevirt-bot kubevirt-bot merged commit 915a19c into kubevirt:release-1.2 May 24, 2024
33 of 34 checks passed
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants