OCPBUGS-61843: UPSTREAM: 131850: cpumanager: uncorecache alignment for odd integer cpus

[ffromani]

Cherry-pick of upstream 131850 to release 4.20

backport notice note the e2e portion of commit 366615b is intentionally stripped as it doesn't apply against 4.20. The reason for this is when 131850 merged upstream kubernetes#130274 was still underway.

[openshift-ci-robot]

@ffromani: This pull request references Jira Issue OCPBUGS-61843, which is invalid:

• expected the bug to target the "4.20.z" version, but no target version was set
• 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 Jira Issue OCPBUGS-61843 to depend on a bug targeting a version in 4.21.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

In response to this:

Cherry-pick of upstream 131850 to release 4.20

backport notice note the e2e portion of commit 366615b is intentionally stripped as it doesn't apply against 4.20. The reason for this is when 131850 merged upstream kubernetes#130274 was still underway.

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]

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

The following commits are valid:

• 366615b|UPSTREAM: 131850: add e2e_node tests for uncore alignment: the upstream PR kubernetes/kubernetes#131850 has merged
• e30217b|UPSTREAM: 131850: fix uncore cache alignment for odd integer cpus: the upstream PR kubernetes/kubernetes#131850 has merged

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

[ffromani]

/retest

[ffromani]

/jira refresh

[openshift-ci-robot]

@ffromani: This pull request references Jira Issue OCPBUGS-61843, which is invalid:

• expected the bug to target the "4.20.z" version, but no target version was set
• 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 Jira Issue OCPBUGS-61843 to depend on a bug targeting a version in 4.21.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

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.

[ffromani]

/jira refresh

[openshift-ci-robot]

@ffromani: This pull request references Jira Issue OCPBUGS-61843, which is invalid:

• expected Jira Issue OCPBUGS-61843 to depend on a bug targeting a version in 4.21.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

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.

[openshift-ci]

@ffromani: 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	366615b	link	false	/test e2e-aws-ovn-techpreview-serial
ci/prow/e2e-aws-ovn-serial	366615b	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-techpreview-serial-2of2	366615b	link	false	/test e2e-aws-ovn-techpreview-serial-2of2

Full PR test history. Your PR dashboard.

Details

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.

[ffromani]

/jira refresh

[openshift-ci-robot]

@ffromani: This pull request references Jira Issue OCPBUGS-61843, 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 type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-69821 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-69821 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 @mrniranjan

Details

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.

[ffromani]

/retest-required

[haircommander]

/lgtm
/label backport-risk-assessed
/verified later @mrniranjan

[haircommander]

cc @bertinatto

[openshift-ci-robot]

@haircommander: This PR has been marked to be verified later by @mrniranjan.

Details

In response to this:

/lgtm
/label backport-risk-assessed
/verified later @mrniranjan

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]

@haircommander: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers]

Details

In response to this:

/lgtm
/label backport-risk-assessed
/verified later @mrniranjan

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.

[rphillips]

/lgtm
/hold consider for the new year? feel free to remove the hold if it's critical.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details

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

[ffromani]

@bertinatto could you PTAL from rebasing perspective? thanks a ton!