E2E: Add test case to check Infrastructure pods affinity#1470
E2E: Add test case to check Infrastructure pods affinity#1470mrniranjan wants to merge 1 commit intoopenshift:mainfrom
Conversation
mrniranjan
force-pushed
the
add_affinity_test
branch
from
ab7000c to
a52170e
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mrniranjan The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| 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
|
@mrniranjan: The following tests failed, say
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. |
2 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