Skip to content

OCPBUGS-81638: Add openshift/disruptive-longrunning testsuite in release-4.21 branch#30976

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
BhargaviGudi:node-longrunning
Apr 9, 2026
Merged

OCPBUGS-81638: Add openshift/disruptive-longrunning testsuite in release-4.21 branch#30976
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
BhargaviGudi:node-longrunning

Conversation

@BhargaviGudi
Copy link
Copy Markdown
Contributor

@BhargaviGudi BhargaviGudi commented Apr 7, 2026

Add openshift/disruptive-longrunning testsuite in release-4.21 branch
related PR: https://github.com/openshift/origin/pull/30648/changes#diff-6f59ac4ffef01ed6ee14ebe27baed2d4eb20e438e60a5a32f42d795ac2683d32

CI job: openshift/release#77488

The test can be executed only after the CI job is merged.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@BhargaviGudi: This pull request explicitly references no jira issue.

Details

In response to this:

Add openshift/disruptive-longrunning testsuite in release-4.21 branch
related PR: https://github.com/openshift/origin/pull/30648/changes#diff-6f59ac4ffef01ed6ee14ebe27baed2d4eb20e438e60a5a32f42d795ac2683d32

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 and p0lyn0mial April 7, 2026 14:56
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 7, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b0c8c138-f94f-475d-bcf5-2f15394c1358

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

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.

@BhargaviGudi
Copy link
Copy Markdown
Contributor Author

/test verify

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

@BhargaviGudi: all tests passed!

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.

@BhargaviGudi
Copy link
Copy Markdown
Contributor Author

@cpmeadors and @ngopalak-redhat Could you please help to review this PR? Thanks

@BhargaviGudi
Copy link
Copy Markdown
Contributor Author

/verified by @BhargaviGudi

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 8, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

/verified by @BhargaviGudi

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.

@BhargaviGudi BhargaviGudi changed the title NO-ISSUE: Add openshift/disruptive-longrunning testsuite in release-4.21 branch OCPBUGS-81638: Add openshift/disruptive-longrunning testsuite in release-4.21 branch Apr 8, 2026
@openshift-ci-robot openshift-ci-robot added the jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. label Apr 8, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 8, 2026

@BhargaviGudi: This pull request references Jira Issue OCPBUGS-81638, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Not a Bug) instead
  • dependent bug OCPNODE-3932 is not in the required OCPBUGS project

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:

Add openshift/disruptive-longrunning testsuite in release-4.21 branch
related PR: https://github.com/openshift/origin/pull/30648/changes#diff-6f59ac4ffef01ed6ee14ebe27baed2d4eb20e438e60a5a32f42d795ac2683d32

CI job: openshift/release#77488

The test can be executed only after the CI job is merged.

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 8, 2026
@BhargaviGudi
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 8, 2026

@BhargaviGudi: This pull request references Jira Issue OCPBUGS-81638, which is invalid:

  • dependent bug OCPNODE-3932 is not in the required OCPBUGS project

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.

@BhargaviGudi
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@BhargaviGudi: This pull request references Jira Issue OCPBUGS-81638, which is invalid:

  • expected Jira Issue OCPBUGS-81638 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

@BhargaviGudi BhargaviGudi changed the title OCPBUGS-81638: Add openshift/disruptive-longrunning testsuite in release-4.21 branch NO-ISSUE: Add openshift/disruptive-longrunning testsuite in release-4.21 branch Apr 8, 2026
@openshift-ci-robot openshift-ci-robot removed jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 8, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@BhargaviGudi: This pull request explicitly references no jira issue.

Details

In response to this:

Add openshift/disruptive-longrunning testsuite in release-4.21 branch
related PR: https://github.com/openshift/origin/pull/30648/changes#diff-6f59ac4ffef01ed6ee14ebe27baed2d4eb20e438e60a5a32f42d795ac2683d32

CI job: openshift/release#77488

The test can be executed only after the CI job is merged.

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.

@cpmeadors
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2026
@petr-muller
Copy link
Copy Markdown
Member

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BhargaviGudi, cpmeadors, petr-muller

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 Apr 9, 2026
@BhargaviGudi BhargaviGudi changed the title NO-ISSUE: Add openshift/disruptive-longrunning testsuite in release-4.21 branch OCPBUGS-81638: Add openshift/disruptive-longrunning testsuite in release-4.21 branch Apr 9, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Apr 9, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@BhargaviGudi: This pull request references Jira Issue OCPBUGS-81638, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-82197 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-82197 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents
Details

In response to this:

Add openshift/disruptive-longrunning testsuite in release-4.21 branch
related PR: https://github.com/openshift/origin/pull/30648/changes#diff-6f59ac4ffef01ed6ee14ebe27baed2d4eb20e438e60a5a32f42d795ac2683d32

CI job: openshift/release#77488

The test can be executed only after the CI job is merged.

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-merge-bot openshift-merge-bot bot merged commit 22ad8ea into openshift:release-4.21 Apr 9, 2026
9 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@BhargaviGudi: Jira Issue Verification Checks: Jira Issue OCPBUGS-81638
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-81638 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Add openshift/disruptive-longrunning testsuite in release-4.21 branch
related PR: https://github.com/openshift/origin/pull/30648/changes#diff-6f59ac4ffef01ed6ee14ebe27baed2d4eb20e438e60a5a32f42d795ac2683d32

CI job: openshift/release#77488

The test can be executed only after the CI job is merged.

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.

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/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants