OCPBUGS-55265: Bump 1.32.4

[dusk125]

No description provided.

[openshift-ci-robot]

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

• expected the bug to target the "4.19.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:

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:

• 01b87d2|Fix implementation of ContainsCIDR to allow non-equal addresses: does not specify an upstream backport in the commit message
• 0b7ab45|Merge pull request #130684 from carlory/automated-cherry-pick-of-#130335-upstream-release-1.32: does not specify an upstream backport in the commit message
• 3571689|Merge pull request #131159 from wojtek-t/automated-cherry-pick-of-#131020-upstream-release-1.32: does not specify an upstream backport in the commit message
• 4142a54|UPSTREAM: : Update openshift-hack/rebase.sh to properly handle delta in go mod go version string: does not specify an upstream backport in the commit message
• 588fb32|Merge tag 'v1.32.4' into bump-1.32.4: does not specify an upstream backport in the commit message
• 59526cd|Release commit for Kubernetes v1.32.4: does not specify an upstream backport in the commit message
• 7b326a9|Fix race for sending errors in watch: does not specify an upstream backport in the commit message
• 9773512|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• a0ad8fb|Update CHANGELOG/CHANGELOG-1.32.md for v1.32.3: does not specify an upstream backport in the commit message
• ad0c8a1|add e2e test to reproduce unexpected unmount after kubelet is restarted: does not specify an upstream backport in the commit message
• b5f6d82|CHANGELOG-1.32: fix release note about kubeadm upgrade phases: does not specify an upstream backport in the commit message
• bf1fded|Merge pull request #130773 from JoelSpeed/automated-cherry-pick-of-#130450-kubernetes-release-1.32: does not specify an upstream backport in the commit message
• cdc807a|Merge pull request #131154 from neolit123/automated-cherry-pick-of-#131153-origin-release-1.32: does not specify an upstream backport in the commit message
• e3daed8|fix handle terminating pvc when kubelet rebuild dsw: does not specify an upstream backport in the commit message
• ef4a6f9|fix e2e: 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

[dusk125]

/jira refresh

[openshift-ci-robot]

@dusk125: This pull request references Jira Issue OCPBUGS-55265, 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.19.0) matches configured target version for branch (4.19.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

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.

[dusk125]

/retest

[openshift-ci]

@bertinatto: Overrode contexts on behalf of bertinatto: ci/prow/verify-deps

Details

In response to this:

/override ci/prow/verify-deps
This job is broken and in the process of being removed.

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]

@dusk125: all tests passed!

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.

[bertinatto]

/label backport-risk-assessed

[bertinatto]

/remove-label backports/unvalidated-commits
/label backports/validated-commits
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, dusk125

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 [bertinatto]

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

[bertinatto]

/label jira/valid-bug
/remove-label jira/invalid-bug

[sdodson]

/label cherry-pick-approved

[openshift-ci-robot]

@dusk125: Jira Issue OCPBUGS-55265: Some pull requests linked via external trackers have merged:

• openshift/kubernetes#2275

The following pull requests linked via external trackers have not merged:

• openshift/origin#29707 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

Details

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.19.0-202505051914.p0.gf6cfe0c.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.19.0-202505051914.p0.gf6cfe0c.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.19.0-202505051914.p0.gf6cfe0c.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-kube-apiserver-artifacts
This PR has been included in build ose-installer-kube-apiserver-artifacts-container-v4.19.0-202505051914.p0.gf6cfe0c.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.19.0-0.nightly-2025-05-07-130416