[release-4.21] OCPBUGS-112011: BUG-FIX Latency Test by openshift-cherrypick-robot · Pull Request #1592 · openshift/cluster-node-tuning-operator

openshift-cherrypick-robot · 2026-08-19T09:48:34Z

This is an automated cherry-pick of #1566

/assign tavital

If LATENCY_TEST_CPUS is not set, the test pod is given almost all of the node's isolated CPUs. On large machines that CPU setup inside the pod can take so long that the old fixed 120-second wait buffer runs out, and the test fails waiting for the pod to finish even though the latency tool itself succeeded. Replace the hard-coded 120s with LATENCY_TEST_TIMEOUT_BUFFER (default 150s) and return a clear error asking to increase it when the wait still times out. Signed-off-by: Tomer Avital <tavital@redhat.com>

openshift-merge-bot · 2026-08-19T09:48:37Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

coderabbitai · 2026-08-19T09:48:46Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f6d88b8a-b153-4c98-9a2b-82add3f7d5cb

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

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

openshift-ci · 2026-08-19T09:49:00Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign ffromani 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

openshift-ci-robot · 2026-08-19T09:49:44Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-98060 has been cloned as Jira Issue OCPBUGS-112011. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-112011: BUG-FIX Latency Test

Details

In response to this:

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 · 2026-08-19T09:49:53Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-98060 to target a version in 4.22.0, but it targets "5.0.0" instead

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:

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 · 2026-08-19T10:05:04Z

@openshift-cherrypick-robot: 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.

tavital · 2026-08-19T11:41:11Z

/jira refresh

openshift-ci-robot · 2026-08-19T11:41:15Z

@tavital: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-98060 to target a version in 4.22.0, but it targets "4.20.z" instead

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:

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.

tavital · 2026-08-19T11:45:24Z

/jira refresh

openshift-ci-robot · 2026-08-19T11:45:28Z

@tavital: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-98060 to target a version in 4.22.0, but it targets "5.0.0" instead

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:

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.

tavital · 2026-08-19T11:46:34Z

/jira refresh

openshift-ci-robot · 2026-08-19T11:46:39Z

@tavital: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-98060 to target a version in 4.22.0, but it targets "5.0.0" instead

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:

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.

tavital · 2026-08-19T12:04:13Z

/jira refresh

openshift-ci-robot · 2026-08-19T12:04:18Z

@tavital: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-98060 to target a version in 4.22.0, but it targets "4.21.z" instead

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:

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.

tavital · 2026-08-19T12:09:45Z

/jira refresh

openshift-ci-robot · 2026-08-19T12:09:49Z

@tavital: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-98060 to target a version in 4.22.0, but it targets "4.21.z" instead

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:

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.

tavital · 2026-08-19T12:15:05Z

/jira refresh

openshift-ci-robot · 2026-08-19T12:15:10Z

@tavital: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-105873 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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:

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.

mrniranjan · 2026-08-19T15:44:20Z

/verified by @mrniranjan

openshift-ci-robot · 2026-08-19T15:44:31Z

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

Details

In response to this:

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.

tavital · 2026-08-24T16:48:59Z

/retest

tavital · 2026-08-24T16:49:33Z

/jira refresh

openshift-ci-robot · 2026-08-24T16:49:38Z

@tavital: This pull request references Jira Issue OCPBUGS-112011, which is invalid:

expected dependent Jira Issue OCPBUGS-105873 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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:

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 assigned tavital Aug 19, 2026

openshift-cherrypick-robot mentioned this pull request Aug 19, 2026

OCPBUGS-98060: BUG-FIX Latency Test #1566

Merged

openshift-ci Bot requested review from MarSik and yanirq August 19, 2026 09:48

openshift-ci Bot changed the title ~~[release-4.21] OCPBUGS-98060: BUG-FIX Latency Test~~ [release-4.21] OCPBUGS-112011: BUG-FIX Latency Test Aug 19, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 19, 2026

Uh oh!

Conversation

openshift-cherrypick-robot commented Aug 19, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 19, 2026

Uh oh!

coderabbitai Bot commented Aug 19, 2026

Review skipped

Uh oh!

openshift-ci Bot commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

openshift-ci Bot commented Aug 19, 2026

Uh oh!

tavital commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

tavital commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

tavital commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

tavital commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

tavital commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

tavital commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

mrniranjan commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

tavital commented Aug 24, 2026

Uh oh!

tavital commented Aug 24, 2026

Uh oh!

openshift-ci-robot commented Aug 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants