Skip to content

Conversation

@dusk125
Copy link
Contributor

@dusk125 dusk125 commented Apr 23, 2025

No description provided.

@openshift-ci-robot openshift-ci-robot added 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 Apr 23, 2025
@openshift-ci-robot
Copy link

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

dusk125 commented Apr 23, 2025

/assign @bertinatto

@dusk125
Copy link
Contributor Author

dusk125 commented Apr 23, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 23, 2025
@openshift-ci-robot
Copy link

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

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

@openshift-ci openshift-ci bot requested review from deads2k, sdodson and wangke19 April 23, 2025 15:13
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Apr 23, 2025
@dusk125
Copy link
Contributor Author

dusk125 commented Apr 25, 2025

/retest

@openshift-trt
Copy link

openshift-trt bot commented May 2, 2025

Job Failure Risk Analysis for sha: 771023c

Job Name Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback High
operator conditions network
This test has passed 98.67% of 2102 runs on release 4.20 [Overall] in the last week.

Open Bugs
Component Readiness: [Networking / cluster-network-operator] [operator-conditions] test regressed
pull-ci-openshift-origin-main-e2e-aws-disruptive Medium
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling High
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded
This test has passed 99.94% of 3080 runs on release 4.20 [Overall] in the last week.

Open Bugs
etcd-scaling jobs failing ~60% of the time
pull-ci-openshift-origin-main-e2e-gcp-disruptive High
[sig-node] static pods should start after being created
This test has passed 99.29% of 3080 runs on release 4.20 [Overall] in the last week.
---
[sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator
This test has passed 100.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:hidden Network:ovn NetworkStack:ipv4 Owner:eng Platform:gcp SecurityMode:default Topology:ha Upgrade:micro-downgrade] in the last week.
---
[sig-node] node-lifecycle detects unexpected not ready node
This test has passed 99.81% of 3080 runs on release 4.20 [Overall] in the last week.

Open Bugs
[sig-node] node-lifecycle detects unexpected not ready node failing on azure serial and upgrade jobs
etcd-scaling jobs failing ~60% of the time

@sdodson
Copy link
Member

sdodson commented May 2, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 2, 2025
@openshift-ci-robot
Copy link

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

  • expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.19.0" instead

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.

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.

@sdodson sdodson changed the base branch from main to release-4.19 May 2, 2025 13:41
@openshift-ci-robot
Copy link

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

  • expected Jira Issue OCPBUGS-55265 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.

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.

@sdodson
Copy link
Member

sdodson commented May 2, 2025

/jira refresh

@openshift-ci-robot
Copy link

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

  • expected Jira Issue OCPBUGS-55265 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.

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 dusk125 changed the title WIP: OCPBUGS-55265: Bump 1.32.4 OCPBUGS-55265: Bump 1.32.4 May 5, 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 May 5, 2025
@sdodson sdodson added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 5, 2025
@sdodson sdodson added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels May 6, 2025
@dusk125
Copy link
Contributor Author

dusk125 commented May 6, 2025

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

/lgtm

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

openshift-ci bot commented May 6, 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

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

/retest-required

Remaining retests: 0 against base HEAD 007ecd3 and 2 for PR HEAD 0e993bf in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 6, 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-aws-ovn-serial-shard-1 771023c link false /test e2e-aws-ovn-serial-shard-1
ci/prow/e2e-aws-ovn-serial-shard-2 771023c link false /test e2e-aws-ovn-serial-shard-2
ci/prow/e2e-vsphere-ovn-etcd-scaling 771023c link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-etcd-scaling 771023c link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-disruptive 771023c link false /test e2e-gcp-disruptive
ci/prow/okd-e2e-gcp 771023c link false /test okd-e2e-gcp
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview 771023c link false /test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
ci/prow/e2e-aws-disruptive 771023c link false /test e2e-aws-disruptive
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback 771023c link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-gcp-ovn-etcd-scaling 771023c link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-openstack-serial 771023c link false /test e2e-openstack-serial
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 771023c link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-azure-ovn-etcd-scaling 771023c link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-gcp-fips-serial 771023c link false /test e2e-gcp-fips-serial
ci/prow/e2e-aws-ovn-serial 771023c link true /test e2e-aws-ovn-serial
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 0e993bf link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-agnostic-ovn-cmd 0e993bf link false /test e2e-agnostic-ovn-cmd

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 1a6d910 into openshift:release-4.19 May 6, 2025
30 of 32 checks passed
@openshift-ci-robot
Copy link

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

Jira Issue OCPBUGS-55265 has 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
Copy link
Contributor

[ART PR BUILD NOTIFIER]

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

@openshift-merge-robot
Copy link
Contributor

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

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.