Skip to content

Conversation

@Tal-or
Copy link
Contributor

@Tal-or Tal-or commented Oct 30, 2025

The test isn't useful when the tested machines are all VMs. It will run efficiently on the d/s pipelines where an actual BM workers are being tested.

@openshift-ci openshift-ci bot requested review from ffromani and jmencak October 30, 2025 09:38
@mrniranjan
Copy link
Contributor

mrniranjan commented Oct 30, 2025

@Tal-or can you extend this skip to other Contexts too ? (except configuration tests)

@Tal-or
Copy link
Contributor Author

Tal-or commented Oct 30, 2025

@Tal-or can you extend this skip to other Contexts too ? (except configuration tests)

Not sure which ones, could you please comment on the relevant contexts?

The test no useful when the tested machines are all VMs.
It will run efficiently on the d/s pipelines where actual BM workers
are being tested.

Signed-off-by: Talor Itzhak <titzhak@redhat.com>
@mrniranjan
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 31, 2025
@mrniranjan
Copy link
Contributor

/retitle OCPBUGS-63724: e2e:llc: skip test when no BM worker is found

@openshift-ci openshift-ci bot changed the title e2e:llc: skip test when no BM worker is found OCPBUGS-63724: e2e:llc: skip test when no BM worker is found Oct 31, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 31, 2025
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mrniranjan

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

In response to this:

The test no useful when the tested machines are all VMs. It will run efficiently on the d/s pipelines where actual BM workers are being tested.

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 a review from mrniranjan October 31, 2025 04:56
@mrniranjan
Copy link
Contributor

/retest

@mrniranjan
Copy link
Contributor

/test e2e-aws-ovn

@Tal-or
Copy link
Contributor Author

Tal-or commented Nov 2, 2025

/retest

@openshift-ci-robot
Copy link
Contributor

@Tal-or: This pull request references Jira Issue OCPBUGS-63724, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mrniranjan

In response to this:

The test isn't useful when the tested machines are all VMs. It will run efficiently on the d/s pipelines where actual BM workers are being tested.

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.

@Tal-or
Copy link
Contributor Author

Tal-or commented Nov 2, 2025

@mrniranjan we need the verify label as well

@mrniranjan
Copy link
Contributor

/verified by @mrniranjan

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 2, 2025
@openshift-ci-robot
Copy link
Contributor

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

In response to this:

/verified by @mrniranjan

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.

@yanirq
Copy link
Contributor

yanirq commented Nov 2, 2025

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Tal-or, yanirq

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

The pull request process is described here

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 Nov 2, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD be65dc6 and 2 for PR HEAD 453b7b7 in total

@ffromani
Copy link
Contributor

ffromani commented Nov 3, 2025

/override ci/prow/e2e-aws-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 3, 2025

@ffromani: Overrode contexts on behalf of ffromani: ci/prow/e2e-aws-ovn

In response to this:

/override ci/prow/e2e-aws-ovn

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.

@Tal-or
Copy link
Contributor Author

Tal-or commented Nov 3, 2025

/cherry-pick release-4.20

@openshift-cherrypick-robot

@Tal-or: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.20

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-ci
Copy link
Contributor

openshift-ci bot commented Nov 3, 2025

@Tal-or: all tests passed!

Full PR test history. Your PR dashboard.

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-bot openshift-merge-bot bot merged commit f472158 into openshift:main Nov 3, 2025
19 checks passed
@openshift-ci-robot
Copy link
Contributor

@Tal-or: Jira Issue Verification Checks: Jira Issue OCPBUGS-63724
✔️ 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-63724 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

The test isn't useful when the tested machines are all VMs. It will run efficiently on the d/s pipelines where an actual BM workers are being tested.

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-cherrypick-robot

@Tal-or: new pull request created: #1422

In response to this:

/cherry-pick release-4.20

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
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-11-03-191704

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

7 participants