Skip to content

OCPBUGS-57861: Bump 4.20 1.32.6 #29934

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
Closed
wants to merge 4 commits into from
Closed

OCPBUGS-57861: Bump 4.20 1.32.6 #29934

wants to merge 4 commits into from

Conversation

dusk125
Copy link
Contributor

@dusk125 dusk125 commented Jun 20, 2025

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 20, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 20, 2025
@openshift-ci-robot
Copy link

@dusk125: This pull request references Jira Issue OCPBUGS-57861, which is valid.

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 POST, 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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 20, 2025
@openshift-ci openshift-ci bot added e2e-images-update Related to images used by e2e tests vendor-update Touching vendor dir or related files labels Jun 20, 2025
@bertinatto
Copy link
Member

/test images

@dusk125 dusk125 force-pushed the bump-4.20-1.32.6 branch from 21d8b7f to 7437219 Compare July 1, 2025 15:53
@dusk125
Copy link
Contributor Author

dusk125 commented Jul 2, 2025

/retest-required

1 similar comment
@dusk125
Copy link
Contributor Author

dusk125 commented Jul 2, 2025

/retest-required

@openshift-ci-robot openshift-ci-robot mentioned this pull request Jul 3, 2025
Merged
@dusk125 dusk125 force-pushed the bump-4.20-1.32.6 branch from 7437219 to 40732a8 Compare July 3, 2025 17:56
@dusk125 dusk125 changed the title WIP: OCPBUGS-57861: Bump 4.20 1.32.6 OCPBUGS-57861: Bump 4.20 1.32.6 Jul 3, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 3, 2025
@wangke19
Copy link
Contributor

wangke19 commented Jul 7, 2025

/retest

bertinatto
bertinatto reviewed Jul 7, 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.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 7, 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 Jul 7, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b2a0f07 and 2 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9ff893a and 1 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f380d1e and 0 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6251391 and 0 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/hold

Revision 40732a8 was retested 3 times: holding

@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 Jul 10, 2025
@dusk125
Copy link
Contributor Author

dusk125 commented Jul 10, 2025

/hold cancel
/retest-required

@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 Jul 10, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 39b65b5 and 2 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7e76cc2 and 1 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 58a3259 and 0 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/hold

Revision 40732a8 was retested 3 times: holding

@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 Jul 11, 2025
@bertinatto
Copy link
Member

/hold cancel
/retest-required

@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 Jul 11, 2025
@bertinatto bertinatto mentioned this pull request Jul 11, 2025
Merged
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 58a3259 and 2 for PR HEAD 40732a8 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 58a3259 and 2 for PR HEAD 40732a8 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6a5d795 and 1 for PR HEAD 40732a8 in total

@bertinatto
Copy link
Member

/retest-required

@wangke19
Copy link
Contributor

/test e2e-aws-ovn-edge-zones

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6a5d795 and 2 for PR HEAD 40732a8 in total

@bertinatto
Copy link
Member

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6a5d795 and 2 for PR HEAD 40732a8 in total

@bertinatto
Copy link
Member

openshift/kubernetes#2314 will be tagged today, so I propose we hold this PR in favor of #29709.

/hold

@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 Jul 15, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 15, 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/e2e-openstack-ovn 40732a8 link false /test e2e-openstack-ovn
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 40732a8 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-gcp-disruptive 40732a8 link false /test e2e-gcp-disruptive
ci/prow/e2e-aws-ovn-single-node-upgrade 40732a8 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-fips-serial-2of2 40732a8 link false /test e2e-gcp-fips-serial-2of2
ci/prow/okd-e2e-gcp 40732a8 link false /test okd-e2e-gcp
ci/prow/e2e-azure-ovn-upgrade 40732a8 link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-azure-ovn-etcd-scaling 40732a8 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-serial-publicnet-1of2 40732a8 link false /test e2e-aws-ovn-serial-publicnet-1of2
ci/prow/e2e-openstack-serial 40732a8 link false /test e2e-openstack-serial
ci/prow/e2e-aws-disruptive 40732a8 link false /test e2e-aws-disruptive
ci/prow/e2e-vsphere-ovn-etcd-scaling 40732a8 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-etcd-scaling 40732a8 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-fips-serial-1of2 40732a8 link false /test e2e-gcp-fips-serial-1of2
ci/prow/e2e-gcp-ovn-etcd-scaling 40732a8 link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-edge-zones 40732a8 link true /test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-ovn-serial-2of2 40732a8 link true /test e2e-aws-ovn-serial-2of2
ci/prow/e2e-aws-ovn-serial-1of2 40732a8 link true /test e2e-aws-ovn-serial-1of2

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-trt openshift-trt
Copy link

openshift-trt bot commented Jul 15, 2025

Job Failure Risk Analysis for sha: 40732a8

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling High
[bz-etcd][invariant] alert/etcdMembersDown should not be at or above info
This test has passed 99.91% of 3468 runs on release 4.20 [Overall] in the last week.

Open Bugs
etcdMembersDown should not fire on healthy etcd scaling event
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling Low
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded
This test has passed 0.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-disruptive Medium
[bz-Etcd] clusteroperator/etcd should not change condition/Available
Potential external regression detected for High Risk Test analysis
---
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis

Open Bugs
[sig-node] static pods should start after being created

1 similar comment
@openshift-trt openshift-trt
Copy link

openshift-trt bot commented Jul 15, 2025

Job Failure Risk Analysis for sha: 40732a8

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling High
[bz-etcd][invariant] alert/etcdMembersDown should not be at or above info
This test has passed 99.91% of 3468 runs on release 4.20 [Overall] in the last week.

Open Bugs
etcdMembersDown should not fire on healthy etcd scaling event
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling Low
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded
This test has passed 0.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-disruptive Medium
[bz-Etcd] clusteroperator/etcd should not change condition/Available
Potential external regression detected for High Risk Test analysis
---
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis

Open Bugs
[sig-node] static pods should start after being created

@bertinatto
Copy link
Member

/close
in favor of #29709

@openshift-ci openshift-ci bot closed this Jul 16, 2025
@openshift-ci-robot
Copy link

@dusk125: This pull request references Jira Issue OCPBUGS-57861. The bug has been updated to no longer 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 OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 16, 2025

@bertinatto: Closed this PR.

In response to this:

/close
in favor of #29709

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.

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

@wangke19 wangke19 Awaiting requested review from wangke19

@deads2k deads2k Awaiting requested review from deads2k

Assignees

@bertinatto bertinatto

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. e2e-images-update Related to images used by e2e tests 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@dusk125 @openshift-ci-robot @bertinatto @wangke19