OCPBUGS-60511: Rebase v1.31.12 to 4.18

[dusk125]

No description provided.

[openshift-ci-robot]

@dusk125: This pull request references Jira Issue OCPBUGS-60511, which is invalid:

• expected the bug to target the "4.18.z" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-60511 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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]

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

• 2e6eaa1|do not allow the node to update it's owner reference: does not specify an upstream backport in the commit message
• 34fa4fa|Merge pull request #133283 from BenTheElder/cherrypick-133262-release-1.31-attempt-2: does not specify an upstream backport in the commit message
• 3691b1d|fix(kubelet): acquire imageRecordsLock when removing image: does not specify an upstream backport in the commit message
• 42be76d|Bump images, dependencies and versions to go 1.23.11 and distroless iptables: does not specify an upstream backport in the commit message
• 4fe5989|Merge pull request #132899 from cpanato/update-go123-131: does not specify an upstream backport in the commit message
• 5691229|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.11: does not specify an upstream backport in the commit message
• 5c8d265|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• a2d98ca|Merge pull request #133470 from natherz97/node-deletion-release-1.31: does not specify an upstream backport in the commit message
• c1e5f4a|Release commit for Kubernetes v1.31.12: does not specify an upstream backport in the commit message
• c5f59d2|Merge tag 'v1.31.12' into release-4.18: does not specify an upstream backport in the commit message
• e561c4c|Merge pull request #131579 from ndbaker1/automated-cherry-pick-of-#131251-origin-release-1.31: does not specify an upstream backport in the commit message
• f662eeb|remove failing test that depends on expired credential, remove credential, add TODOs: 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.

[dusk125]

/assign @bertinatto

[openshift-ci-robot]

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

• 2e6eaa1|do not allow the node to update it's owner reference: does not specify an upstream backport in the commit message
• 34fa4fa|Merge pull request #133283 from BenTheElder/cherrypick-133262-release-1.31-attempt-2: does not specify an upstream backport in the commit message
• 3691b1d|fix(kubelet): acquire imageRecordsLock when removing image: does not specify an upstream backport in the commit message
• 42be76d|Bump images, dependencies and versions to go 1.23.11 and distroless iptables: does not specify an upstream backport in the commit message
• 4f965d8|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• 4fe5989|Merge pull request #132899 from cpanato/update-go123-131: does not specify an upstream backport in the commit message
• 5691229|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.11: does not specify an upstream backport in the commit message
• a2d98ca|Merge pull request #133470 from natherz97/node-deletion-release-1.31: does not specify an upstream backport in the commit message
• c1e5f4a|Release commit for Kubernetes v1.31.12: does not specify an upstream backport in the commit message
• c5f59d2|Merge tag 'v1.31.12' into release-4.18: does not specify an upstream backport in the commit message
• e561c4c|Merge pull request #131579 from ndbaker1/automated-cherry-pick-of-#131251-origin-release-1.31: does not specify an upstream backport in the commit message
• f662eeb|remove failing test that depends on expired credential, remove credential, add TODOs: 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: dusk125
Once this PR has been reviewed and has the lgtm label, please ask for approval from bertinatto. For more information see the 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

[bertinatto]

/test ?

[openshift-ci]

@bertinatto: The following commands are available to trigger required jobs:

/test artifacts

/test configmap-scale

/test e2e-aws-crun-wasm

/test e2e-aws-jenkins

/test e2e-aws-ovn-cgroupsv2

/test e2e-aws-ovn-crun

/test e2e-aws-ovn-downgrade

/test e2e-aws-ovn-fips

/test e2e-aws-ovn-runc

/test e2e-aws-ovn-serial

/test e2e-aws-ovn-upgrade

/test e2e-azure-ovn-upgrade

/test e2e-gcp

/test e2e-gcp-ovn-upgrade

/test e2e-metal-ipi-ovn-ipv6

/test images

/test integration

/test k8s-e2e-conformance-aws

/test k8s-e2e-gcp-ovn

/test k8s-e2e-gcp-serial

/test okd-scos-images

/test perfscale-control-plane-6nodes

/test unit

/test verify

/test verify-commits

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd

/test e2e-aws

/test e2e-aws-csi

/test e2e-aws-disruptive

/test e2e-aws-ovn

/test e2e-aws-single-node

/test e2e-azure

/test e2e-external-aws-ccm

/test e2e-metal-ipi-ovn-dualstack

/test e2e-openstack

/test e2e-openstack-csi-cinder

/test e2e-openstack-csi-manila

/test e2e-vsphere

/test k8s-e2e-aws

/test k8s-e2e-aws-ovn-serial

/test k8s-e2e-gcp-five-control-plane-replicas

/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-kubernetes-release-4.18-artifacts

pull-ci-openshift-kubernetes-release-4.18-e2e-agnostic-ovn-cmd

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-crun-wasm

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-csi

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-cgroupsv2

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-crun

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-downgrade

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-fips

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-runc

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-serial

pull-ci-openshift-kubernetes-release-4.18-e2e-aws-ovn-upgrade

pull-ci-openshift-kubernetes-release-4.18-e2e-azure-ovn-upgrade

pull-ci-openshift-kubernetes-release-4.18-e2e-gcp

pull-ci-openshift-kubernetes-release-4.18-e2e-gcp-ovn-upgrade

pull-ci-openshift-kubernetes-release-4.18-images

pull-ci-openshift-kubernetes-release-4.18-integration

pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-aws-ovn-serial

pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-conformance-aws

pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-gcp-ovn

pull-ci-openshift-kubernetes-release-4.18-k8s-e2e-gcp-serial

pull-ci-openshift-kubernetes-release-4.18-okd-scos-e2e-aws-ovn

pull-ci-openshift-kubernetes-release-4.18-okd-scos-images

pull-ci-openshift-kubernetes-release-4.18-unit

pull-ci-openshift-kubernetes-release-4.18-verify

pull-ci-openshift-kubernetes-release-4.18-verify-commits

In response to this:

/test ?

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.

[bertinatto]

/test e2e-metal-ipi-ovn-ipv6

[dusk125]

/retest

[bertinatto]

/hold
for openshift/release#68559

[bertinatto]

/retest

[bertinatto]

/retest

[bertinatto]

/retest

[wallylewis]

/retest-required

[openshift-ci]

@dusk125: 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-metal-ipi-ovn-ipv6	4f965d8	link	true	/test e2e-metal-ipi-ovn-ipv6

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

[openshift-ci-robot]

@dusk125: Jira Issue OCPBUGS-60511: All pull requests linked via external trackers have merged:

• openshift/kubernetes#2427
• openshift/kubernetes#2440

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

In response to this:

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.