OCPBUGS-16348: OSLAT latency spikes due to tsc karg setting

[browsell]

Signed-off-by: Brent Rowsell browsell@redhat.com

A RHEL 9.x change added a timer to make sure TSC_adjust is always which introduces latency spikes. Update tsc karg to tsc=reliable. This aligns with the realtime tuned profile.

[openshift-ci-robot]

@browsell: This pull request references Jira Issue OCPBUGS-16348, which is invalid:

• expected the bug to target the "4.14.0" version, but no target version was set

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.

In response to this:

Signed-off-by: Brent Rowsell browsell@redhat.com

A RHEL 9.x change added a timer to make sure TSC_adjust is always which introduces latency spikes. Update tsc karg to tsc=reliable. This aligns with the realtime tuned profile.

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/test-infra repository.

[browsell]

/retest

[browsell]

/test unit

[browsell]

/test e2e-gcp-pao-workloadhints

[openshift-ci]

@browsell: 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/test-infra repository. I understand the commands that are listed here.

[browsell]

/jira refresh

[openshift-ci-robot]

@browsell: This pull request references Jira Issue OCPBUGS-16348, which is invalid:

• expected the bug to target the "4.14.0" version, but no target version was set

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.

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 kubernetes/test-infra repository.

[browsell]

/jira refresh

[openshift-ci-robot]

@browsell: This pull request references Jira Issue OCPBUGS-16348, which is invalid:

• expected the bug to target the "4.14.0" version, but no target version was set

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.

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 kubernetes/test-infra repository.

[browsell]

/jira refresh

[openshift-ci-robot]

@browsell: This pull request references Jira Issue OCPBUGS-16348, 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.14.0) matches configured target version for branch (4.14.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gsr-shanks

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 kubernetes/test-infra repository.

[jmencak]

Based on the OCPBUG
/assign @MarSik

[yanirq]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: browsell, 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:

• OWNERS [yanirq]

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]

@browsell: Jira Issue OCPBUGS-16348: All pull requests linked via external trackers have merged:

• openshift/cluster-node-tuning-operator#756

Jira Issue OCPBUGS-16348 has been moved to the MODIFIED state.

In response to this:

Signed-off-by: Brent Rowsell browsell@redhat.com

A RHEL 9.x change added a timer to make sure TSC_adjust is always which introduces latency spikes. Update tsc karg to tsc=reliable. This aligns with the realtime tuned profile.

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/test-infra repository.

[yanirq]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@yanirq: #756 failed to apply on top of branch "release-4.13":

Applying: OCPBUGS-16348: OSLAT latency spikes due to tsc karg setting Signed-off-by: Brent Rowsell <browsell@redhat.com>
Applying: OCPBUGS-16348: Update Unit test Signed-off-by: Brent Rowsell browsell@redhat.com
Applying: OCPBUGS-16348: OSLAT latency spikes due to tsc karg setting Signed-off-by: Brent Rowsell <browsell@redhat.com>
Using index info to reconstruct a base tree...
A	test/e2e/performanceprofile/functests/8_performance_workloadhints/workloadhints.go
M	test/e2e/performanceprofile/testdata/render-expected-output/manual_tuned.yaml
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/performanceprofile/testdata/render-expected-output/manual_tuned.yaml
CONFLICT (modify/delete): test/e2e/performanceprofile/functests/8_performance_workloadhints/workloadhints.go deleted in HEAD and modified in OCPBUGS-16348: OSLAT latency spikes due to tsc karg setting Signed-off-by: Brent Rowsell <browsell@redhat.com>. Version OCPBUGS-16348: OSLAT latency spikes due to tsc karg setting Signed-off-by: Brent Rowsell <browsell@redhat.com> of test/e2e/performanceprofile/functests/8_performance_workloadhints/workloadhints.go left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0003 OCPBUGS-16348: OSLAT latency spikes due to tsc karg setting Signed-off-by: Brent Rowsell <browsell@redhat.com>
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.13

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/test-infra repository.