Skip to content

[release-4.21] OCPBUGS-77147: Add config override for openflow-probe#2917

Open
arkadeepsen wants to merge 1 commit intoopenshift:release-4.21from
arkadeepsen:ovs-bundle-timeout-release-4.21
Open

[release-4.21] OCPBUGS-77147: Add config override for openflow-probe#2917
arkadeepsen wants to merge 1 commit intoopenshift:release-4.21from
arkadeepsen:ovs-bundle-timeout-release-4.21

Conversation

@arkadeepsen
Copy link
Member

@arkadeepsen arkadeepsen commented Mar 3, 2026

Manual cherry pick from #2916 (commit 119a5bc). No conflicts.

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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 Mar 3, 2026
@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: This pull request references Jira Issue OCPBUGS-77147, which is invalid:

  • expected dependent Jira Issue OCPBUGS-76500 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Manual cherry pick from #2916 (commit 119a5bc)

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.

@coderabbitai
Copy link

coderabbitai bot commented Mar 3, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 687f62ac-d604-4502-b9bf-17bd96ad9793

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@arkadeepsen
Copy link
Member Author

/retest-required

@liqcui
Copy link

liqcui commented Mar 3, 2026

/verified by @liqcui

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 3, 2026
@openshift-ci-robot
Copy link
Contributor

@liqcui: This PR has been marked as verified by @liqcui.

Details

In response to this:

/verified by @liqcui

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.

@pperiyasamy
Copy link
Member

/retest-required

1 similar comment
@arkadeepsen
Copy link
Member Author

/retest-required

@pperiyasamy
Copy link
Member

/lgtm

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

@arkadeepsen: This pull request references Jira Issue OCPBUGS-77147, which is invalid:

  • expected dependent Jira Issue OCPBUGS-76500 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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:

Manual cherry pick from #2916 (commit 119a5bc). No conflicts.

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.

@arkadeepsen arkadeepsen force-pushed the ovs-bundle-timeout-release-4.21 branch from cd14da6 to 311fab6 Compare March 4, 2026 13:48
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Mar 4, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2026
@danwinship
Copy link
Contributor

/lgtm

@liqcui
Copy link

liqcui commented Mar 4, 2026

/verified by @liqcui

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

@liqcui: This PR has been marked as verified by @liqcui.

Details

In response to this:

/verified by @liqcui

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 lgtm Indicates that a PR is ready to be merged. label Mar 4, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arkadeepsen, danwinship, pperiyasamy

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 Mar 4, 2026
@arkadeepsen
Copy link
Member Author

@danwinship Can you please also add the backport-risk-assessed label?

@danwinship
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 4, 2026
@arkadeepsen
Copy link
Member Author

/test e2e-aws-ovn-windows
/test e2e-gcp-ovn-upgrade

@arkadeepsen
Copy link
Member Author

In e2e-metal-ipi-ovn-ipv6-ipsec the actual test step passed, but the must-gather step failed after the test step.

@arkadeepsen
Copy link
Member Author

/test e2e-aws-ovn-hypershift-conformance
/test e2e-metal-ipi-ovn-dualstack-bgp

@arkadeepsen
Copy link
Member Author

/test e2e-metal-ipi-ovn-ipv6-ipsec

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 5, 2026

@arkadeepsen: 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/4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-upgrade 311fab6 link false /test 4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-upgrade
ci/prow/security 311fab6 link false /test security
ci/prow/e2e-aws-ovn-hypershift-conformance 311fab6 link true /test e2e-aws-ovn-hypershift-conformance

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.

@arkadeepsen
Copy link
Member Author

/test e2e-aws-ovn-hypershift-conformance

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.