[release-4.5] Bug 1846451: UPSTREAM: 90419: update strategy used to reuse CPUs from init containers in CPUManager #25310

cynepco3hahue · 2020-07-23T10:15:41Z

Signed-off-by: Artyom Lukianov alukiano@redhat.com

…ers in CPUManager ref: kubernetes/kubernetes#90419 Signed-off-by: Artyom Lukianov <alukiano@redhat.com>

openshift-ci-robot · 2020-07-23T10:15:46Z

@cynepco3hahue: This pull request references Bugzilla bug 1846451, which is invalid:

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (CURRENTRELEASE) 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.

cynepco3hahue · 2020-07-23T10:21:39Z

/hold depends on #25273

cynepco3hahue · 2020-07-26T08:44:04Z

/retest

cynepco3hahue · 2020-07-26T08:48:42Z

/hold cancel

vpickard

Changes match upstream
/lgtm

sjenning · 2020-08-05T14:41:11Z

/approve

openshift-ci-robot · 2020-08-05T14:41:29Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cynepco3hahue, sjenning, vpickard

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

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

openshift-bot · 2020-08-06T01:00:26Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-08-06T01:00:30Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-08-07T01:00:57Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-08-07T01:01:01Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-08-09T01:03:54Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-08-09T01:03:58Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-08-12T01:00:49Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-08-12T01:00:53Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-08-13T01:00:43Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-08-13T01:00:47Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED 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-09-15T01:00:55Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-09-16T01:00:37Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-16T01:00:41Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-09-17T01:01:23Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-17T01:01:26Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-09-18T01:01:32Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-18T01:01:35Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-09-19T01:00:47Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-19T01:00:51Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-09-21T01:00:45Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-21T01:00:48Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-09-22T01:01:21Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-22T01:01:25Z

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

expected dependent Bugzilla bug 1846428 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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-09-23T01:00:43Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-23T01:00:48Z

@openshift-bot: This pull request references Bugzilla bug 1846451, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.5.z) matches configured target release for branch (4.5.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1846428 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
dependent Bugzilla bug 1846428 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.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.

cynepco3hahue · 2020-09-23T12:31:56Z

@sjenning Can I please get the cherry-pick-approved label?

sjenning · 2020-09-23T17:05:36Z

@cynepco3hahue that is the job of the patch-manager.

However, I will say they hesitate to approve medium severity bzs for z-stream release.

markmc · 2020-09-25T10:15:55Z

(patch manager here)

Right, I'm vaguely aware of the justification for this backport, but it would have been nice to see that written down in the bz

knobunc · 2020-09-26T00:44:40Z

/retest

openshift-bot · 2020-09-26T00:52:38Z

/retest

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

openshift-bot · 2020-09-26T02:22:39Z

/retest

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

openshift-bot · 2020-09-26T04:45:38Z

/retest

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

openshift-bot · 2020-09-26T05:50:40Z

/retest

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

openshift-bot · 2020-09-26T07:08:41Z

/retest

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

openshift-bot · 2020-09-26T07:22:31Z

/retest

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

openshift-ci-robot · 2020-09-26T09:35:44Z

@cynepco3hahue: All pull requests linked via external trackers have merged:

openshift/origin#25310

Bugzilla bug 1846451 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.

UPSTREAM: 90419: update strategy used to reuse CPUs from init contain…

0f5abee

…ers in CPUManager ref: kubernetes/kubernetes#90419 Signed-off-by: Artyom Lukianov <alukiano@redhat.com>

openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jul 23, 2020

openshift-ci-robot requested review from deads2k and tbielawa July 23, 2020 10:16

openshift-ci-robot added the vendor-update Touching vendor dir or related files label Jul 23, 2020

openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 23, 2020

openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 26, 2020

vpickard reviewed Aug 5, 2020

View reviewed changes

openshift-ci-robot assigned vpickard Aug 5, 2020

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

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

openshift-ci-robot removed the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Aug 12, 2020

openshift-ci-robot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Aug 12, 2020

openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Sep 23, 2020

markmc added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 25, 2020

openshift-merge-robot merged commit 970c1b3 into openshift:release-4.5 Sep 26, 2020

[release-4.5] Bug 1846451: UPSTREAM: 90419: update strategy used to reuse CPUs from init containers in CPUManager #25310

[release-4.5] Bug 1846451: UPSTREAM: 90419: update strategy used to reuse CPUs from init containers in CPUManager #25310

Conversation

cynepco3hahue commented Jul 23, 2020

openshift-ci-robot commented Jul 23, 2020

cynepco3hahue commented Jul 23, 2020

cynepco3hahue commented Jul 26, 2020

cynepco3hahue commented Jul 26, 2020

vpickard left a comment

Choose a reason for hiding this comment

sjenning commented Aug 5, 2020

openshift-ci-robot commented Aug 5, 2020

openshift-bot commented Aug 6, 2020

openshift-ci-robot commented Aug 6, 2020

openshift-bot commented Aug 7, 2020

openshift-ci-robot commented Aug 7, 2020

openshift-bot commented Aug 9, 2020

openshift-ci-robot commented Aug 9, 2020

openshift-bot commented Aug 12, 2020

openshift-ci-robot commented Aug 12, 2020

openshift-bot commented Aug 13, 2020

openshift-ci-robot commented Aug 13, 2020

openshift-ci-robot commented Sep 15, 2020

openshift-bot commented Sep 16, 2020

openshift-ci-robot commented Sep 16, 2020

openshift-bot commented Sep 17, 2020

openshift-ci-robot commented Sep 17, 2020

openshift-bot commented Sep 18, 2020

openshift-ci-robot commented Sep 18, 2020

openshift-bot commented Sep 19, 2020

openshift-ci-robot commented Sep 19, 2020

openshift-bot commented Sep 21, 2020

openshift-ci-robot commented Sep 21, 2020

openshift-bot commented Sep 22, 2020

openshift-ci-robot commented Sep 22, 2020

openshift-bot commented Sep 23, 2020

openshift-ci-robot commented Sep 23, 2020

cynepco3hahue commented Sep 23, 2020

sjenning commented Sep 23, 2020

markmc commented Sep 25, 2020

knobunc commented Sep 26, 2020

openshift-bot commented Sep 26, 2020

openshift-bot commented Sep 26, 2020

openshift-bot commented Sep 26, 2020

openshift-bot commented Sep 26, 2020

openshift-bot commented Sep 26, 2020

openshift-bot commented Sep 26, 2020

openshift-ci-robot commented Sep 26, 2020