OCPBUGS-104855: Fix PPC example CPU counts for HT compatibility (4.19)

[kquinn1204]

Version(s):
4.19

Issue:
https://redhat.atlassian.net/browse/OCPBUGS-104855

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

Cherry-pick of fc42ec6 from PR #117426 (main branch).

The PPC example command used --reserved-cpu-count=1 and --offlined-cpu-count=1, which fails on hyper-threading systems (the default) with:

Error: failed to make profile data from node handler: failed to compute the reserved and isolated CPUs: can't allocate odd number of CPUs from a NUMA Node

Changes:

1. Changes --reserved-cpu-count from 1 to 2 for HT NUMA compatibility.
2. Removes --offlined-cpu-count from the example (on a 4-CPU system, 2 reserved + 2 offlined = 0 isolated, which is invalid).
3. Updates example output to reflect corrected CPU allocations.

Note: This backport retains the level=info msg="..." log format used by PPC in 4.19. The v4.20+ PPC: ... format update is in PR #117426 (main) only.

[openshift-ci-robot]

@kquinn1204: This pull request references Jira Issue OCPBUGS-104855, 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 Jira Issue OCPBUGS-104855 to depend on a bug 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:

Version(s):
4.19

Issue:
https://redhat.atlassian.net/browse/OCPBUGS-104855

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

Cherry-pick of fc42ec6 from PR #117426 (main branch).

The PPC example command used --reserved-cpu-count=1 and --offlined-cpu-count=1, which fails on hyper-threading systems (the default) with:

Error: failed to make profile data from node handler: failed to compute the reserved and isolated CPUs: can't allocate odd number of CPUs from a NUMA Node

Changes:

1. Changes --reserved-cpu-count from 1 to 2 for HT NUMA compatibility.
2. Removes --offlined-cpu-count from the example (on a 4-CPU system, 2 reserved + 2 offlined = 0 isolated, which is invalid).
3. Updates example output to reflect corrected CPU allocations.

Note: This backport retains the level=info msg="..." log format used by PPC in 4.19. The v4.20+ PPC: ... format update is in PR #117426 (main) only.

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.

[ocpdocs-previewbot]

🤖 Mon Aug 10 15:05:20 - Prow CI generated the docs preview:

https://117457--ocpdocs-pr.netlify.app/openshift-enterprise/latest/scalability_and_performance/cnf-tuning-low-latency-nodes-with-perf-profile.html

[openshift-ci-robot]

@kquinn1204: This pull request references Jira Issue OCPBUGS-104855, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
• 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-104855 to depend on a bug 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:

Version(s):
4.19

Issue:
https://redhat.atlassian.net/browse/OCPBUGS-104855

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

Cherry-pick of fc42ec6 from PR #117426 (main branch).

The PPC example command used --reserved-cpu-count=1 and --offlined-cpu-count=1, which fails on hyper-threading systems (the default) with:

Error: failed to make profile data from node handler: failed to compute the reserved and isolated CPUs: can't allocate odd number of CPUs from a NUMA Node

Changes:

1. Changes --reserved-cpu-count from 1 to 2 for HT NUMA compatibility.
2. Removes --offlined-cpu-count from the example (on a 4-CPU system, 2 reserved + 2 offlined = 0 isolated, which is invalid).
3. Updates example output to reflect corrected CPU allocations.

Note: This backport retains the level=info msg="..." log format used by PPC in 4.19. The v4.20+ PPC: ... format update is in PR #117426 (main) only.

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]

@kquinn1204: all tests passed!

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.