Skip to content

OCPBUGS-56436: Bump 4.20 1.32.5 #2308

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.

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

Merged
merged 16 commits into from
May 27, 2025

Conversation

dusk125
Copy link

@dusk125 dusk125 commented May 21, 2025

No description provided.

k8s-release-robot and others added 16 commits April 22, 2025 16:22
Co-authored-by: Hemant Kumar <[email protected]>
Signed-off-by: carlory <[email protected]>
Bump images, dependencies, versions to Go 1.23.8
Bump distroless-iptables to 0.6.9

Signed-off-by: Arnaud Meukam <[email protected]>
…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.
[release-1.32][go] Bump images, dependencies and versions to go 1.23.8 and distroless iptables
…ck-of-#131418-upstream-release-1.32

Automated cherry pick of kubernetes#131418: Check for newer fields when deciding expansion recovery feature status
…ck-of-#131495-release-1.32

Automated cherry pick of kubernetes#131495: Handle unsupported node expansion for RWX volumes
Kubernetes official release v1.32.5
@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/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 21, 2025
@openshift-ci-robot
Copy link

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

Requesting review from QA contact:
/cc @wangke19

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.

@dusk125
Copy link
Author

dusk125 commented May 21, 2025

/assign @bertinatto

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

@openshift-ci openshift-ci bot requested review from wangke19, benluddy and tkashem May 21, 2025 15:08
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label May 21, 2025
@dusk125
Copy link
Author

dusk125 commented May 21, 2025

/retest-required

@bertinatto
Copy link
Member

/retest

1 similar comment
@wangke19
Copy link

/retest

@bertinatto
Copy link
Member

/retest-required

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
/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. labels May 22, 2025
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

/test ?

Copy link

openshift-ci bot commented May 22, 2025

@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-hypershift
/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 images
/test integration
/test k8s-e2e-conformance-aws
/test k8s-e2e-gcp-ovn
/test k8s-e2e-gcp-serial
/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-ovn-techpreview
/test e2e-aws-ovn-techpreview-serial
/test e2e-aws-single-node
/test e2e-azure
/test e2e-external-aws-ccm
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/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
/test okd-scos-images

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

pull-ci-openshift-kubernetes-master-artifacts
pull-ci-openshift-kubernetes-master-e2e-agnostic-ovn-cmd
pull-ci-openshift-kubernetes-master-e2e-aws-crun-wasm
pull-ci-openshift-kubernetes-master-e2e-aws-csi
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-crun
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-downgrade
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-fips
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-hypershift
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-runc
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-serial
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-techpreview
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-techpreview-serial
pull-ci-openshift-kubernetes-master-e2e-aws-ovn-upgrade
pull-ci-openshift-kubernetes-master-e2e-azure-ovn-upgrade
pull-ci-openshift-kubernetes-master-e2e-gcp
pull-ci-openshift-kubernetes-master-e2e-gcp-ovn-upgrade
pull-ci-openshift-kubernetes-master-images
pull-ci-openshift-kubernetes-master-integration
pull-ci-openshift-kubernetes-master-k8s-e2e-aws-ovn-serial
pull-ci-openshift-kubernetes-master-k8s-e2e-conformance-aws
pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-ovn
pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-serial
pull-ci-openshift-kubernetes-master-okd-scos-e2e-aws-ovn
pull-ci-openshift-kubernetes-master-unit
pull-ci-openshift-kubernetes-master-verify
pull-ci-openshift-kubernetes-master-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
Copy link
Member

/test e2e-metal-ipi-ovn-ipv6

@bertinatto
Copy link
Member

/payload-job periodic-ci-openshift-release-master-nightly-4.20-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
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.20-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c3998590-3713-11f0-9be5-2fdd6279244a-0

@bertinatto
Copy link
Member

/test e2e-metal-ipi-ovn-ipv6

Copy link

openshift-ci bot commented May 26, 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 e00e45a link true /test k8s-e2e-gcp-ovn
ci/prow/e2e-gcp e00e45a link true /test e2e-gcp
ci/prow/k8s-e2e-gcp-serial e00e45a link true /test k8s-e2e-gcp-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-sigs/prow repository. I understand the commands that are listed here.

@bertinatto
Copy link
Member

/test e2e-metal-ipi-ovn-ipv6

@bertinatto
Copy link
Member

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

Copy link

openshift-ci bot commented May 26, 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.20-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9a6fa860-3a57-11f0-92ea-6c2112d860d9-0

@bertinatto
Copy link
Member

@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.20-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9a6fa860-3a57-11f0-92ea-6c2112d860d9-0

This passed.

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 26, 2025
@bertinatto
Copy link
Member

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 4cd5657 into openshift:master May 27, 2025
28 of 29 checks passed
@openshift-ci-robot
Copy link

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

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

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-56436 has not 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.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

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

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

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

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

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

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

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

@dusk125 dusk125 deleted the bump-4.20-1.32.5 branch May 27, 2025 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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
Development

Successfully merging this pull request may close these issues.