Skip to content

WINC-1971: [ote] Add proxy suite for node-proxy tests - #4459

Draft
rrasouli wants to merge 1 commit into
openshift:masterfrom
rrasouli:winc-1971-ote-proxy-suite
Draft

WINC-1971: [ote] Add proxy suite for node-proxy tests#4459
rrasouli wants to merge 1 commit into
openshift:masterfrom
rrasouli:winc-1971-ote-proxy-suite

Conversation

@rrasouli

Copy link
Copy Markdown
Contributor

Summary

Adds a windows-machine-config-operator/proxy OTE suite that inherits from openshift/disruptive to run OTP tests tagged with [node-proxy] on vsphere proxy clusters.

Changes

  • Added proxy suite with Parents: ["openshift/disruptive"] and qualifier name.contains("[node-proxy]")
  • Picks up 4 existing OTP tests: 65980, 66670, 68320, 71173

Related

The proxy suite inherits from openshift/disruptive to pick up
OTP tests tagged with [node-proxy] on vsphere proxy clusters.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 13, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 13, 2026

Copy link
Copy Markdown

@rrasouli: This pull request references WINC-1971 which is a valid jira issue.

Details

In response to this:

Summary

Adds a windows-machine-config-operator/proxy OTE suite that inherits from openshift/disruptive to run OTP tests tagged with [node-proxy] on vsphere proxy clusters.

Changes

  • Added proxy suite with Parents: ["openshift/disruptive"] and qualifier name.contains("[node-proxy]")
  • Picks up 4 existing OTP tests: 65980, 66670, 68320, 71173

Related

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 Aug 13, 2026
@openshift-ci

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Excluded labels (none allowed) (2)
  • do-not-merge/work-in-progress
  • do-not-merge/hold

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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 12b97507-50d6-4353-ba17-0dab8a77d470

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

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.

@openshift-ci

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rrasouli

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 Aug 13, 2026
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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants