NO-ISSUE: Add openshift/disruptive-longrunning testsuite in release-4.21 branch

[BhargaviGudi]

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]

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

[coderabbitai]

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: ee1758f0-0377-49a9-af49-d410be91e9da

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[BhargaviGudi]

/test verify

[openshift-ci]

@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]

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

[BhargaviGudi]

/verified by @BhargaviGudi

[openshift-ci-robot]

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

[openshift-ci-robot]

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

[BhargaviGudi]

/jira refresh

[openshift-ci-robot]

@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]

/jira refresh

[openshift-ci-robot]

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

[openshift-ci-robot]

@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]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BhargaviGudi, cpmeadors
Once this PR has been reviewed and has the lgtm label, please assign dennisperiquet for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment