OCPBUGS-61187: [4.20] carry patch to disable DisableCPUQuotaWithExclusiveCPUs

[haircommander]

What type of PR is this?

What this PR does / why we need it:

inspired by #1956

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

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

[openshift-ci-robot]

@haircommander: This pull request references Jira Issue OCPBUGS-61187, 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-62165 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Won't Do) 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:

What type of PR is this?

What this PR does / why we need it:

inspired by #1956

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

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]

@haircommander: 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:

• 0487c31|UPSTREAM: : carry patch to disable DisableCPUQuotaWithExclusiveCPUs: 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: haircommander
Once this PR has been reviewed and has the lgtm label, please assign p0lyn0mial for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[haircommander]

/skip
/retest-required

[haircommander]

/retest-required

[haircommander]

/retest

[openshift-ci]

@haircommander: 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	0487c31	link	false	/test e2e-aws-ovn-techpreview-serial
ci/prow/e2e-aws-ovn-techpreview	0487c31	link	false	/test e2e-aws-ovn-techpreview
ci/prow/k8s-e2e-aws-ovn-serial	0487c31	link	false	/test k8s-e2e-aws-ovn-serial
ci/prow/okd-scos-e2e-aws-ovn	0487c31	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-serial	0487c31	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-runc	0487c31	link	true	/test e2e-aws-ovn-runc

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.