Revert "Update to Kubernetes 1.27.4"

[dgoodwin]

Reverts #1645

Suspected of multiple regressions: TRT-1179

[openshift-ci-robot]

@dgoodwin: This pull request references Jira Issue OCPBUGS-16166, 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:

Reverts #1645

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.

[openshift-ci-robot]

@dgoodwin: 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:

• 62f59a5|Revert "OCPBUGS-16166: Update to Kubernetes 1.27.4": does not specify an upstream backport in the commit message

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dgoodwin
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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]

@dgoodwin: This pull request references Jira Issue OCPBUGS-16166, 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.

In response to this:

Reverts #1645

Suspected of multiple regressions: TRT-1179

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.

[openshift-ci-robot]

@dgoodwin: This pull request references Jira Issue OCPBUGS-16166, 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.

In response to this:

Reverts #1645

Suspected of multiple regressions: TRT-1179

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.

[dgoodwin]

/payload-aggregate periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-aws-ovn-conformance 10
/payload-job periodic-ci-openshift-release-master-ci-4.14-e2e-aws-sdn-techpreview-serial

[openshift-ci]

@dgoodwin: trigger 2 job(s) for the /payload-(job|aggregate) command

• periodic-ci-openshift-release-master-ci-4.14-e2e-aws-sdn-techpreview-serial
• periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/37c62da0-31f4-11ee-9bd8-9afe1d94a4c3-0

[openshift-ci-robot]

@dgoodwin: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Reverts #1645

Suspected of multiple regressions: TRT-1179

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.

[dgoodwin]

/test unit
/test verify

Fabio confirms this is a go 1.20 problem they're working on, and retesting multiple times should help.

[dgoodwin]

/test unit
/test verify

[openshift-ci]

@dgoodwin: The following tests 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-agnostic-ovn-cmd	62f59a5	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/verify-commits	62f59a5	link	true	/test verify-commits
ci/prow/k8s-e2e-conformance-aws	62f59a5	link	true	/test k8s-e2e-conformance-aws
ci/prow/e2e-gcp-ovn-upgrade	62f59a5	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/verify	62f59a5	link	true	/test verify
ci/prow/e2e-aws-ovn-fips	62f59a5	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-serial	62f59a5	link	true	/test e2e-aws-ovn-serial

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.

[dgoodwin]

/close

[openshift-ci]

@dgoodwin: Closed this PR.

In response to this:

/close

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.