OCPBUGS-61515: UPSTREAM: 135372: Re-enable temporarily disabled SchedulerPreemption test

[ingvagabund]

Pulling kubernetes#135372 in

[openshift-ci-robot]

@ingvagabund: This pull request references Jira Issue OCPBUGS-61515, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Pulling kubernetes#135372 in

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ingvagabund: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 7936c45|UPSTREAM: : Re-enable temporarily disabled SchedulerPreemption test: does not specify an upstream backport in the commit message
• de36d08|UPSTREAM: 135372: fix(SchedulerPreemption/Async): schedule all medium priority pods first so all low priority pods can be preempted: the upstream PR kubernetes/kubernetes#135372 has not yet merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[ingvagabund]

Checking https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_kubernetes/2524/pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-serial/1991545177520476160:

Kubernetes e2e suite: [It] [sig-scheduling] SchedulerPreemption [Serial] validates various priority Pods preempt expectedly with the async preemption [Feature:SchedulerAsyncPreemption] [FeatureGate:SchedulerAsyncPreemption] [Beta]

passed in 1m55s.

[ingvagabund]

/retest-required

[openshift-ci-robot]

@ingvagabund: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• cfa45c7|UPSTREAM: 135372: fix(SchedulerPreemption/Async): schedule all medium priority pods first so all low priority pods can be preempted: the upstream PR kubernetes/kubernetes#135372 has not yet merged
• de36d08|UPSTREAM: 135372: fix(SchedulerPreemption/Async): schedule all medium priority pods first so all low priority pods can be preempted: the upstream PR kubernetes/kubernetes#135372 has not yet merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[ingvagabund]

Based on https://www.kubernetes.dev/resources/release/#kubernetes-v135 the release is scheduled for Dec 17. The upstream fix is not that critical for the release so likely the fix will not get merged soon.

[ingvagabund]

Merged upstream

[ingvagabund]

/retest-required

[ingvagabund]

/verified by ci/prow/k8s-e2e-gcp-serial

[openshift-ci-robot]

@ingvagabund: This PR has been marked as verified by ci/prow/k8s-e2e-gcp-serial.

Details

In response to this:

/verified by ci/prow/k8s-e2e-gcp-serial

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 openshift-eng/jira-lifecycle-plugin repository.

[ingvagabund]

/validate-backports

[openshift-ci-robot]

@ingvagabund: the contents of this pull request could be automatically validated.

The following commits are valid:

• cfa45c7|UPSTREAM: 135372: fix(SchedulerPreemption/Async): schedule all medium priority pods first so all low priority pods can be preempted: the upstream PR kubernetes/kubernetes#135372 has merged
• de36d08|UPSTREAM: 135372: fix(SchedulerPreemption/Async): schedule all medium priority pods first so all low priority pods can be preempted: the upstream PR kubernetes/kubernetes#135372 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[p0lyn0mial]

lgtm

should we squash the commits ?

[ingvagabund]

/label tide/merge-method-squash

[p0lyn0mial]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, p0lyn0mial

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS [p0lyn0mial]

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

[ingvagabund]

/jira refresh

[openshift-ci-robot]

@ingvagabund: This pull request references Jira Issue OCPBUGS-61515, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[ingvagabund]

/jira refresh

[openshift-ci-robot]

@ingvagabund: This pull request references Jira Issue OCPBUGS-61515, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @kasturinarra

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 76cb1db and 2 for PR HEAD cfa45c7 in total

[ingvagabund]

/retest-required

[openshift-ci]

@ingvagabund: 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
ci/prow/e2e-aws-ovn-techpreview-serial-2of2	cfa45c7	link	false	/test e2e-aws-ovn-techpreview-serial-2of2

Full PR test history. Your PR dashboard.

Details

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.

[ingvagabund]

/retest-required

[ingvagabund]

/cherry-pick release-4.21

[openshift-cherrypick-robot]

@ingvagabund: once the present PR merges, I will cherry-pick it on top of release-4.21 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.21

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.

[openshift-ci-robot]

@ingvagabund: Jira Issue Verification Checks: Jira Issue OCPBUGS-61515
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-61515 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Pulling kubernetes#135372 in

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-cherrypick-robot]

@ingvagabund: new pull request created: #2556

Details

In response to this:

/cherry-pick release-4.21

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.