Skip to content

WIP : Patch test#1401

Open
PannagaRao wants to merge 5 commits intoopenshift:mainfrom
PannagaRao:patch-test
Open

WIP : Patch test#1401
PannagaRao wants to merge 5 commits intoopenshift:mainfrom
PannagaRao:patch-test

Conversation

@PannagaRao
Copy link
Contributor

@PannagaRao PannagaRao commented Feb 7, 2026

Only for testing purposes

@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 Feb 7, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: PannagaRao

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 Feb 7, 2026
Pannaga Rao Bhoja Ramamanohara and others added 2 commits February 7, 2026 01:18
Install LeaderWorkerSet v0.8.0 from GitHub releases instead of using
the OLM stable-v1.0 channel. This ensures the same LWS version is used
as upstream Kueue tests, which properly supports maxSurge rolling updates
with status.Replicas surge handling.
CI pre-installs LWS v1.0.0 via OLM subscription before running e2e tests.
The e2e-upstream-test target now:
1. Removes OLM-installed LWS components (if present)
2. Installs LWS v0.8.0 from GitHub releases
3. Waits for controller readiness
4. Runs tests

This ensures upstream e2e tests use the same LWS version (v0.8.0) as
upstream CI, which properly handles maxSurge rolling updates.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@PannagaRao
Copy link
Contributor Author

/retest

1 similar comment
@PannagaRao
Copy link
Contributor Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Feb 7, 2026

@PannagaRao: 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/test-e2e-upstream-4-20 b93541c link true /test test-e2e-upstream-4-20
ci/prow/test-e2e-upstream-4-21 b93541c link true /test test-e2e-upstream-4-21

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.

@openshift-merge-robot
Copy link

PR needs rebase.

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 13, 2026
@coderabbitai
Copy link

coderabbitai bot commented Feb 13, 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.

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.

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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants