Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.9] Bug 2013653: TuneD: workaround for high CPU utilization of [scheduler] plug-in. #279

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #278

/assign jmencak

The fix for rhbz#1979352 introduced the [scheduler] plug-in as a
standard part of openshift TuneD profiles.  Unfortunately, the
[scheduler] plug-in can be very CPU intensive, especially on the
OpenShift platform.  The bug for this issue is tracked by rhbz#1921738.
Until this is fixed, work around this problem by adding "runtime=0"
[scheduler] plug-in option.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2021

@openshift-cherrypick-robot: Bugzilla bug 2013321 has been cloned as Bugzilla bug 2013653. Retitling PR to link against new bug.
/retitle [release-4.9] Bug 2013653: TuneD: workaround for high CPU utilization of [scheduler] plug-in.

In response to this:

[release-4.9] Bug 2013321: TuneD: workaround for high CPU utilization of [scheduler] plug-in.

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.

@openshift-ci openshift-ci bot changed the title [release-4.9] Bug 2013321: TuneD: workaround for high CPU utilization of [scheduler] plug-in. [release-4.9] Bug 2013653: TuneD: workaround for high CPU utilization of [scheduler] plug-in. Oct 13, 2021
@openshift-ci openshift-ci bot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Oct 13, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2021

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2013653, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2013321 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Bugzilla bug 2013321 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (skordas@redhat.com), skipping review request.

In response to this:

[release-4.9] Bug 2013653: TuneD: workaround for high CPU utilization of [scheduler] plug-in.

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.

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Oct 13, 2021
@jmencak
Copy link
Contributor

jmencak commented Oct 13, 2021

/lgtm

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

jmencak commented Oct 13, 2021

/approve

@openshift-ci openshift-ci bot requested a review from jmencak October 13, 2021 13:21
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak, openshift-cherrypick-robot

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 requested a review from kpouget October 13, 2021 13:21
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2021
@jmencak
Copy link
Contributor

jmencak commented Oct 13, 2021

@mrunalp , can we have staff-eng-approved label for this? Thank you!

@jmencak
Copy link
Contributor

jmencak commented Oct 13, 2021

/test e2e-aws-operator

@jmencak
Copy link
Contributor

jmencak commented Oct 13, 2021

/test e2e-aws

@jmencak
Copy link
Contributor

jmencak commented Oct 13, 2021

/test e2e-upgrade

@jmencak
Copy link
Contributor

jmencak commented Oct 13, 2021

/retest

@sdodson sdodson added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 14, 2021
@openshift-merge-robot openshift-merge-robot merged commit 2a863dc into openshift:release-4.9 Oct 14, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2021

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2013653 has been moved to the MODIFIED state.

In response to this:

[release-4.9] Bug 2013653: TuneD: workaround for high CPU utilization of [scheduler] plug-in.

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.

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. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants