OCPBUGS-13579: Bump minKubeVersion to 1.27

[ingvagabund]

SSIA

[openshift-ci-robot]

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

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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.

In response to this:

SSIA

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/test-infra repository.

[ingvagabund]

/jira refresh

[openshift-ci-robot]

@ingvagabund: This pull request references Jira Issue OCPBUGS-13579, which is valid.

3 validation(s) were run on this bug

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

Requesting review from QA contact:
/cc @kasturinarra

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 kubernetes/test-infra repository.

[atiratree]

/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b52bf63 and 2 for PR HEAD dd0737c in total

[ingvagabund]

I0619 12:07:04.616515   10295 operator_test.go:218] Descheduler (operand) pod running in descheduler-7688bf94cd-cfx49
--- FAIL: TestDescheduling (60.50s)
    ...
    operator_test.go:389: Pod test-descheduler-operator-pod-7bc7bff7f-cnknn not running yet, is Pending instead
    operator_test.go:389: Pod test-descheduler-operator-pod-7bc7bff7f-cnknn not running yet, is Pending instead
I0619 12:08:02.075635       1 schedule_one.go:252] "Successfully bound pod to node" pod="e2e-testdescheduling/test-descheduler-operator-pod-7bc7bff7f-cnknn" node="ip-10-0-183-55.us-west-1.compute.internal" evaluatedNodes=6 feasibleNodes=3

looks like it just took longer to schedule the pod

[ingvagabund]

/retest-required

[ingvagabund]

/retest-required

[openshift-ci]

@ingvagabund: all tests passed!

Full PR test history. Your PR dashboard.

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

[atiratree]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [ingvagabund]

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

[openshift-ci-robot]

@ingvagabund: Jira Issue OCPBUGS-13579: All pull requests linked via external trackers have merged:

• openshift/cluster-capacity#73
• openshift/descheduler#92
• openshift/cluster-kube-descheduler-operator#298
• openshift/cluster-policy-controller#113
• openshift/cluster-kube-controller-manager-operator#737
• openshift/cluster-kube-controller-manager-operator#738
• openshift/cluster-kube-descheduler-operator#299

Jira Issue OCPBUGS-13579 has been moved to the MODIFIED state.

In response to this:

SSIA

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/test-infra repository.