[release-4.20] OCPBUGS-63601: Skip CPU resource status for workload-partitioning

[harche]

…inned pods

What type of PR is this?

/kind bug

What this PR does / why we need it:

Manual cherry pick of #2490

Which issue(s) this PR is related to:

Fixes https://issues.redhat.com/browse/OCPBUGS-63601

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Fixed CPU double-counting issue for workload-partitioned pods that caused false "Insufficient cpu"
  scheduling errors when InPlacePodVerticalScaling is enabled.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[openshift-ci-robot]

@harche: This pull request references Jira Issue OCPBUGS-63601, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-62270 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.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

…inned pods

What type of PR is this?

/kind bug

What this PR does / why we need it:

Manual cherry pick of #2490

Which issue(s) this PR is related to:

Fixes https://issues.redhat.com/browse/OCPBUGS-63601

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Fixed CPU double-counting issue for workload-partitioned pods that caused false "Insufficient cpu"
 scheduling errors when InPlacePodVerticalScaling is enabled.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

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]

@harche: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 897567e|[release-4.20] OCPBUGS-63601: Skip CPU resource status for workload-pinned pods: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[harche]

/jira refresh

[openshift-ci-robot]

@harche: This pull request references Jira Issue OCPBUGS-63601, which is invalid:

• expected dependent Jira Issue OCPBUGS-62270 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.

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 openshift-eng/jira-lifecycle-plugin repository.

[sdodson]

/remove-label backports/unvalidated-commits

[sdodson]

/retest-required

[sdodson]

/test e2e-aws-ovn-serial
This job is mostly just timing out, presumbits haven't gotten the sharding that happens in post submits so we should probably just rely on that to confirm no regressions in 4.21 and then move forward with this.

[rphillips]

/approve
/verified by @harche

[haircommander]

/lgtm

[openshift-ci-robot]

@rphillips: This PR has been marked as verified by @harche.

In response to this:

/approve
/verified by @harche

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, harche, rphillips

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:

• pkg/kubelet/DOWNSTREAM_OWNERS [rphillips]

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

[rphillips]

/label backport-risk-assessed

[rphillips]

/jira refresh

[openshift-ci-robot]

@rphillips: This pull request references Jira Issue OCPBUGS-63601, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-62270 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-62270 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
• bug has dependents

Requesting review from QA contact:
/cc @lyman9966

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 openshift-eng/jira-lifecycle-plugin repository.

[rphillips]

/hold for a CI build

[openshift-ci]

@harche: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-techpreview-serial	897567e	link	false	/test e2e-aws-ovn-techpreview-serial
ci/prow/e2e-aws-ovn-techpreview	897567e	link	false	/test e2e-aws-ovn-techpreview
ci/prow/verify-commits	897567e	link	true	/test verify-commits
ci/prow/e2e-aws-ovn-serial	897567e	link	true	/test e2e-aws-ovn-serial

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-sigs/prow repository. I understand the commands that are listed here.

[sdodson]

/close
commit fixed in #2499

[openshift-ci]

@sdodson: Closed this PR.

In response to this:

/close
commit fixed in #2499

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.

[openshift-ci-robot]

@harche: This pull request references Jira Issue OCPBUGS-63601. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

…inned pods

What type of PR is this?

/kind bug

What this PR does / why we need it:

Manual cherry pick of #2490

Which issue(s) this PR is related to:

Fixes https://issues.redhat.com/browse/OCPBUGS-63601

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Fixed CPU double-counting issue for workload-partitioned pods that caused false "Insufficient cpu"
 scheduling errors when InPlacePodVerticalScaling is enabled.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

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.