RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

A correction to the Additional info section:
============================================


- The issue is seen with/without HT.
- That is, an issue is seen when allocating 3 CPU cores (Hyperthreaded or not) but not with 4 CPU cores, with or without HT


HT enabled (again, 3 cores issue is visible and 4 cores, no issue is seen)
==========
 - pinned to a single thread from the core, we cannot see the issue.
 - pinned to 2 threads from the same core, we can see the issue.

HT disabled
===========
 - pinned to 3 individual cores = can see the issue
 - pinned to 4 individual cores = no issue.

We have a similar u/s issue related to the CPU throttling for containers with exclusive CPUs - https://github.com/kubernetes/kubernetes/issues/70585.

If that is the issue, then the CPU quota can be disabled on OCP with PAO using an annotation on the workload pod and the proper runtime class:

Make sure the pod has the following annotation set: 

annotations:
    cpu-quota.crio.io: "disable"

and that the runtimeClassName is defined in the pod:

spec:
    runtimeClassName: <name of performance class from oc get performanceprofile's status section>