Bug 1822770: Normalize CPU requests on masters #825

openshift-cherrypick-robot · 2020-04-14T08:08:35Z

This is an automated cherry-pick of #796

/assign soltysh

The kube-apiserver uses approximately 33% of master CPU in a reasonable medium sized workload. Given a 1 core per master baseline (since CPU is compressible and shared), assign the kube-apiserver roughly 33% of that core on each master.

openshift-ci-robot · 2020-04-14T08:08:38Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1812709, which is invalid:

expected the bug to target the "4.3.z" release, but it targets "4.4.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-ci-robot · 2020-04-14T08:09:40Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

soltysh

/lgtm
/approve
/assign @mfojtik

openshift-bot · 2020-04-15T01:00:56Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-15T01:00:59Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-16T01:01:29Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-16T01:01:32Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-17T01:01:13Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-17T01:01:16Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-18T01:01:35Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-18T01:02:13Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-19T01:01:29Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-19T01:01:32Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-20T01:01:28Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-20T01:01:31Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-21T01:00:44Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-21T01:00:46Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-22T01:00:52Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-22T01:00:55Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-23T01:01:03Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-23T01:01:07Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

openshift-bot · 2020-04-24T01:01:24Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-04-24T01:01:27Z

@openshift-bot: This pull request references Bugzilla bug 1822770, which is invalid:

expected dependent Bugzilla bug 1812583 to target a release in 4.4.0, 4.4.z, but it targets "4.5.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

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

ingvagabund · 2020-04-29T15:45:17Z

/bugzilla refresh

openshift-ci-robot · 2020-04-29T15:45:22Z

@ingvagabund: This pull request references Bugzilla bug 1822770, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.3.z) matches configured target release for branch (4.3.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1812709 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
dependent Bugzilla bug 1812709 targets the "4.4.0" release, which is one of the valid target releases: 4.4.0, 4.4.z
bug has dependents

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

ingvagabund · 2020-04-29T15:49:52Z

/approve

mfojtik · 2020-05-04T10:18:24Z

/approve

openshift-ci-robot · 2020-05-04T10:18:47Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, mfojtik, openshift-cherrypick-robot, soltysh

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~~ [mfojtik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

sdodson · 2020-05-08T13:43:53Z

/retitle Bug 1822770: Normalize CPU requests on masters

openshift-bot · 2020-05-08T15:09:08Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-ci-robot · 2020-05-08T16:26:20Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: openshift/cluster-kube-apiserver-operator#825, openshift/cluster-kube-controller-manager-operator#395, openshift/cluster-kube-scheduler-operator#239, openshift/cluster-openshift-apiserver-operator#351. Bugzilla bug 1822770 has been moved to the MODIFIED state.

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

kube-apiserver: Normalize CPU requests on masters

708bad2

The kube-apiserver uses approximately 33% of master CPU in a reasonable medium sized workload. Given a 1 core per master baseline (since CPU is compressible and shared), assign the kube-apiserver roughly 33% of that core on each master.

openshift-ci-robot assigned soltysh Apr 14, 2020

openshift-cherrypick-robot mentioned this pull request Apr 14, 2020

[release-4.4] Bug 1812709: Normalize CPU requests on masters #796

Merged

openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 14, 2020

openshift-ci-robot requested review from deads2k and soltysh April 14, 2020 08:09

soltysh changed the title ~~[release-4.3] [release-4.4] Bug 1812709: Normalize CPU requests on masters~~ [release-4.3] Bug 1822770: Normalize CPU requests on masters Apr 14, 2020

openshift-ci-robot assigned mfojtik Apr 14, 2020

soltysh approved these changes Apr 14, 2020

View reviewed changes

openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2020

openshift-ci-robot added the bugzilla/urgent label Apr 18, 2020

openshift-ci-robot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. and removed bugzilla/urgent labels Apr 29, 2020

openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Apr 29, 2020

openshift-ci-robot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 29, 2020

This was referenced May 1, 2020

[release-4.3] Bug 1822770: Normalize CPU requests on masters openshift/cluster-kube-scheduler-operator#239

Merged

[release-4.3] Bug 1822770: Normalize CPU requests on masters openshift/cluster-kube-controller-manager-operator#395

Merged

openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 4, 2020

sdodson added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 8, 2020

openshift-ci-robot changed the title ~~[release-4.3] Bug 1822770: Normalize CPU requests on masters~~ Bug 1822770: Normalize CPU requests on masters May 8, 2020

openshift-ci-robot mentioned this pull request May 8, 2020

Bug 1822770: Normalize CPU requests on masters openshift/cluster-openshift-apiserver-operator#351

Merged

openshift-merge-robot merged commit 0da3940 into openshift:release-4.3 May 8, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bug 1822770: Normalize CPU requests on masters #825

Bug 1822770: Normalize CPU requests on masters #825

openshift-cherrypick-robot commented Apr 14, 2020

openshift-ci-robot commented Apr 14, 2020

openshift-ci-robot commented Apr 14, 2020

soltysh left a comment

openshift-bot commented Apr 15, 2020

openshift-ci-robot commented Apr 15, 2020

openshift-bot commented Apr 16, 2020

openshift-ci-robot commented Apr 16, 2020

openshift-bot commented Apr 17, 2020

openshift-ci-robot commented Apr 17, 2020

openshift-bot commented Apr 18, 2020

openshift-ci-robot commented Apr 18, 2020

openshift-bot commented Apr 19, 2020

openshift-ci-robot commented Apr 19, 2020

openshift-bot commented Apr 20, 2020

openshift-ci-robot commented Apr 20, 2020

openshift-bot commented Apr 21, 2020

openshift-ci-robot commented Apr 21, 2020

openshift-bot commented Apr 22, 2020

openshift-ci-robot commented Apr 22, 2020

openshift-bot commented Apr 23, 2020

openshift-ci-robot commented Apr 23, 2020

openshift-bot commented Apr 24, 2020

openshift-ci-robot commented Apr 24, 2020

ingvagabund commented Apr 29, 2020

openshift-ci-robot commented Apr 29, 2020

ingvagabund commented Apr 29, 2020

mfojtik commented May 4, 2020

openshift-ci-robot commented May 4, 2020

sdodson commented May 8, 2020

openshift-bot commented May 8, 2020

openshift-ci-robot commented May 8, 2020

Bug 1822770: Normalize CPU requests on masters #825

Bug 1822770: Normalize CPU requests on masters #825

Conversation

openshift-cherrypick-robot commented Apr 14, 2020

openshift-ci-robot commented Apr 14, 2020

openshift-ci-robot commented Apr 14, 2020

soltysh left a comment

Choose a reason for hiding this comment

openshift-bot commented Apr 15, 2020

openshift-ci-robot commented Apr 15, 2020

openshift-bot commented Apr 16, 2020

openshift-ci-robot commented Apr 16, 2020

openshift-bot commented Apr 17, 2020

openshift-ci-robot commented Apr 17, 2020

openshift-bot commented Apr 18, 2020

openshift-ci-robot commented Apr 18, 2020

openshift-bot commented Apr 19, 2020

openshift-ci-robot commented Apr 19, 2020

openshift-bot commented Apr 20, 2020

openshift-ci-robot commented Apr 20, 2020

openshift-bot commented Apr 21, 2020

openshift-ci-robot commented Apr 21, 2020

openshift-bot commented Apr 22, 2020

openshift-ci-robot commented Apr 22, 2020

openshift-bot commented Apr 23, 2020

openshift-ci-robot commented Apr 23, 2020

openshift-bot commented Apr 24, 2020

openshift-ci-robot commented Apr 24, 2020

ingvagabund commented Apr 29, 2020

openshift-ci-robot commented Apr 29, 2020

ingvagabund commented Apr 29, 2020

mfojtik commented May 4, 2020

openshift-ci-robot commented May 4, 2020

sdodson commented May 8, 2020

openshift-bot commented May 8, 2020

openshift-ci-robot commented May 8, 2020