Skip to content

Conversation

dgoodwin
Copy link
Contributor

@dgoodwin dgoodwin commented Sep 4, 2025

This is failing too often on gcp and aws jobs where nothing else failed. Informational only, so we'll leave it a flake for now.

This is failing too often on gcp and aws jobs where nothing else failed. Informational only, so we'll leave it a flake for now.
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 4, 2025
@dgoodwin dgoodwin changed the title Mark etcd net overload logging test as a flake OCPBUGS-61194: Mark etcd net overload logging test as a flake Sep 4, 2025
@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 Sep 4, 2025
@openshift-ci-robot
Copy link

@dgoodwin: This pull request references Jira Issue OCPBUGS-61194, which is invalid:

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

In response to this:

This is failing too often on gcp and aws jobs where nothing else failed. Informational only, so we'll leave it a flake for now.

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.

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Sep 4, 2025

/verified later @dgoodwin

This change is inconsequential and triggering a flake is difficult, we need to merge and let soak to ensure it works, but the change is extremely simple and should be no problem.

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Sep 4, 2025

/cherry-pick release-4.20

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Sep 4, 2025
@openshift-cherrypick-robot

@dgoodwin: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.20

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-robot
Copy link

@dgoodwin: This PR has been marked to be verified later by @dgoodwin.

In response to this:

/verified later @dgoodwin

This change is inconsequential and triggering a flake is difficult, we need to merge and let soak to ensure it works, but the change is extremely simple and should be no problem.

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.

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Sep 4, 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 Sep 4, 2025
@openshift-ci-robot
Copy link

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

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.

@smg247
Copy link
Member

smg247 commented Sep 4, 2025

/lgtm

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

openshift-ci bot commented Sep 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, smg247

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

Copy link
Contributor

openshift-ci bot commented Sep 4, 2025

@dgoodwin: 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-disruptive a67668c link false /test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-single-node a67668c link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-kube-apiserver-rollout a67668c link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-csi a67668c link false /test e2e-aws-csi
ci/prow/e2e-aws-proxy a67668c link false /test e2e-aws-proxy
ci/prow/okd-scos-e2e-aws-ovn a67668c link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-ovn-techpreview-serial-1of2 a67668c link false /test e2e-gcp-ovn-techpreview-serial-1of2
ci/prow/e2e-openstack-ovn a67668c link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-serial a67668c link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-dualstack a67668c link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn-single-node-upgrade a67668c link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-cgroupsv2 a67668c link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2 a67668c link false /test e2e-metal-ipi-serial-ovn-ipv6-2of2

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-merge-bot openshift-merge-bot bot merged commit b2728f8 into openshift:main Sep 4, 2025
34 of 47 checks passed
@openshift-ci-robot
Copy link

@dgoodwin: Jira Issue OCPBUGS-61194: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-61194 has been moved to the MODIFIED state.

In response to this:

This is failing too often on gcp and aws jobs where nothing else failed. Informational only, so we'll leave it a flake for now.

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-cherrypick-robot

@dgoodwin: new pull request created: #30214

In response to this:

/cherry-pick release-4.20

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-09-08-035253

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. 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. verified Signifies that the PR passed pre-merge verification criteria verified-later
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants