Skip to content

OCPBUGS-56437: Bump 4.19 1.32.5 #2304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 16 commits into
base: release-4.19
Choose a base branch
from
Open

OCPBUGS-56437: Bump 4.19 1.32.5 #2304

wants to merge 16 commits into from

Conversation

dusk125
Copy link

@dusk125 dusk125 commented May 19, 2025

No description provided.

k8s-release-robot and others added 13 commits April 22, 2025 16:22
@k8s-release-robot
Update CHANGELOG/CHANGELOG-1.32.md for v1.32.4
d5df907
@princepereira
Fix for HNS local endpoint was being deleted instead of the remote en…
76bf5db 
…dpoint.
@gnufied
Check for newer fields when deciding expansion recovery feature status
0bec23c
@gnufied
Also change final status by removing featuregate check
69e0af3
@gnufied
Mark NodeExpansion finsihed without featuregate check
cdbea02
@princepereira
Manually adding fix for failing pull-kubernetes-typecheck tests which…
b23e637 
… had dependency with this commit: kubernetes@6186303
@carlory @gnufied
Handle unsupported node expansion for RWX volumes
5ad726c 
Co-authored-by: Hemant Kumar <[email protected]>
Signed-off-by: carlory <[email protected]>
@ameukam
Bump images, dependencies and versions
7ba9778 
Bump images, dependencies, versions to Go 1.23.8
Bump distroless-iptables to 0.6.9

Signed-off-by: Arnaud Meukam <[email protected]>
@k8s-ci-robot
Merge pull request kubernetes#131428 from princepereira/automated-che…
a624d76 
…rry-pick-of-#131138-upstream-release-1.32

Automated cherry pick of kubernetes#131138: Fix for HNS local endpoint was being deleted instead of the remote endpoint.
@k8s-ci-robot
Merge pull request kubernetes#131528 from ameukam/update-go-1-23-8
01aff80 
[release-1.32][go] Bump images, dependencies and versions to go 1.23.8 and distroless iptables
@k8s-ci-robot
Merge pull request kubernetes#131438 from gnufied/automated-cherry-pi…
55a2f43 
…ck-of-#131418-upstream-release-1.32

Automated cherry pick of kubernetes#131418: Check for newer fields when deciding expansion recovery feature status
@k8s-ci-robot
Merge pull request kubernetes#131524 from carlory/automated-cherry-pi…
3f75cae 
…ck-of-#131495-release-1.32

Automated cherry pick of kubernetes#131495: Handle unsupported node expansion for RWX volumes
@k8s-release-robot
Release commit for Kubernetes v1.32.5
9894294
@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 19, 2025
@openshift-ci-robot
Copy link

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

  • expected Jira Issue OCPBUGS-56437 to depend on a bug targeting a version in 4.20.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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
Copy link

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

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

@dusk125
Copy link
Author

dusk125 commented May 19, 2025

/assign @bertinatto

@openshift-ci openshift-ci bot requested review from jerpeter1 and p0lyn0mial May 19, 2025 19:57
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label May 19, 2025
@dusk125 dusk125 force-pushed the bump-4.19-1.32.5 branch from bb745bb to 01fefa3 Compare May 21, 2025 15:35
@openshift-ci-robot
Copy link

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

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

@dusk125
Copy link
Author

dusk125 commented May 21, 2025

/retest-required

1 similar comment
@bertinatto
Copy link
Member

/retest-required

@bertinatto
Copy link
Member

/test e2e-metal-ipi-ovn-ipv6

@bertinatto
Copy link
Member

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm

/hold
This job must pass. Metal jobs usually are picky about image changes.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 22, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented May 22, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6af1caf0-3714-11f0-8e93-81881759d13e-0

bertinatto
bertinatto reviewed May 22, 2025
View reviewed changes
Copy link
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The conflicting file matches with upstream:

$ git diff v1.32.5 -- pkg/volume/util/operationexecutor/node_expander_test.go

/remove-label backports/unvalidated-commits
/remove-label jira/invalid-bug
/label backports/validated-commits
/lgtm

@openshift-ci openshift-ci bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. lgtm Indicates that a PR is ready to be merged. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 22, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented May 22, 2025

[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

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 22, 2025
@bertinatto
Copy link
Member

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm

@bertinatto
Copy link
Member

/test e2e-metal-ipi-ovn-ipv6

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented May 27, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/88cbb0c0-3afe-11f0-80d5-252c261a6a6c-0

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented May 27, 2025

@dusk125: 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/k8s-e2e-gcp-ovn 01fefa3 link true /test k8s-e2e-gcp-ovn
ci/prow/e2e-gcp 01fefa3 link true /test e2e-gcp
ci/prow/okd-scos-e2e-aws-ovn 01fefa3 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-csi 01fefa3 link false /test e2e-aws-csi
ci/prow/k8s-e2e-gcp-serial 01fefa3 link true /test k8s-e2e-gcp-serial
ci/prow/e2e-gcp-ovn-upgrade 01fefa3 link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn-ipv6 01fefa3 link false /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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bertinatto bertinatto bertinatto left review comments

@jerpeter1 jerpeter1 Awaiting requested review from jerpeter1

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

Assignees

@bertinatto bertinatto

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
9 participants
@dusk125 @openshift-ci-robot @bertinatto @k8s-release-robot @princepereira @gnufied @carlory @ameukam @k8s-ci-robot