OCPBUGS-77377: E2E: Add test case to check Infrastructure pods affinity#1470
Conversation
mrniranjan
force-pushed
the
add_affinity_test
branch
from
ab7000c to
a52170e
Compare
| Expect(reservedCPUSet.IsSubsetOf(maskSet)).To(Equal(true), fmt.Sprintf("The init process (pid 1) should have cpu affinity: %s", reservedCPU)) | ||
| }) | ||
|
|
||
| It("[test_id:87722][crit:high][level:acceptance] verify Infrastructure pods have cpu affinity of reserved plus isolated cpuset", func() { |
There was a problem hiding this comment.
This is only valid when workload partitioning is not enabled. And it is only valid when strict cpu isolation is false in cpu manager.
There was a problem hiding this comment.
I have added a condition to check affinity when workload partitioning is enabled.
Add test case to check affinity of Infrastructure pods. we use tuned as an example to check if the infrastructure pods have the affinity of reserved plus available isolated cpus Signed-off-by: Niranjan M.R <mniranja@redhat.com>
mrniranjan
force-pushed
the
add_affinity_test
branch
from
a52170e to
6a87f37
Compare
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MarSik, mrniranjan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
mrniranjan
changed the title
openshift-ci-robot
added
jira/valid-reference
|
@mrniranjan: This pull request references Jira Issue OCPBUGS-77377, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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: GitHub didn't allow me to request PR reviews from the following users: mrniranjan. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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. |
|
/verified by @mrniranjan |
openshift-ci-robot
added
the
verified
|
@mrniranjan: This PR has been marked as verified by DetailsIn response to this:
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. |
|
@mrniranjan: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@mrniranjan: Jira Issue Verification Checks: Jira Issue OCPBUGS-77377 Jira Issue OCPBUGS-77377 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
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. |
|
/cherry-pick release-4.21 |
|
@mrniranjan: new pull request created: #1476 DetailsIn response to this:
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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-03-02-153725 |
6 participants
Add test case to check affinity of Infrastructure pods. we use tuned as an example to check if the infrastructure pods have the affinity of reserved plus available isolated cpus