New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CNF-9173: e2e: mixedcpus test #892
CNF-9173: e2e: mixedcpus test #892
Conversation
@Tal-or: This pull request references CNF-9173 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In 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/test-infra repository. |
depends on cri-o/cri-o#7608 |
9194a1b
to
a57ec98
Compare
@Tal-or: This pull request references CNF-9173 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In 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/test-infra repository. |
@Tal-or: This pull request references CNF-9173 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In 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/test-infra repository. |
12ffc0d
to
1510113
Compare
/hold |
/test e2e-aws-ovn-techpreview |
8356653
to
257c1d7
Compare
test/e2e/performanceprofile/functests/11_mixedcpus/mixedcpus.go
Outdated
Show resolved
Hide resolved
test/e2e/performanceprofile/functests/11_mixedcpus/mixedcpus.go
Outdated
Show resolved
Hide resolved
257c1d7
to
628dcd1
Compare
628dcd1
to
10a9a43
Compare
@Tal-or: This pull request references CNF-9173 which is a valid jira issue. In 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. |
2dad186
to
db4015d
Compare
/retest |
2527030
to
aa4c3b0
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ffromani, Tal-or The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This test changes the shared cpuset under the profile, wait for mcp to catchup, and checks if the container has been updated to reflect the new shared cpuset. Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Use `mustParse` to make sure we assert in case of invalid cpuset string Signed-off-by: Talor Itzhak <titzhak@redhat.com>
The controller file names on cgroupv1 are different than the one on cgroupv2. This is a pure copy-paste mistake. Signed-off-by: Talor Itzhak <titzhak@redhat.com>
69cdb14
to
9362e00
Compare
LGTM |
9362e00
to
4d77c46
Compare
* Check the len returned from split * Use `GinkgoHelper()` Signed-off-by: Talor Itzhak <titzhak@redhat.com>
4d77c46
to
9bd0341
Compare
/cherry-pick release-4.15 |
@Tal-or: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you. In 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/test-infra repository. |
indeed they are, and they're part of the TP so when imported to Polarion the ids will get generated and I'll consider to add them accordingly. /lgtm |
Thanks @shajmakh I'm doing some local tests on 4.15 and will remove the hold if they are passing |
/hold cancel |
@Tal-or: all tests passed! Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
@Tal-or: #892 failed to apply on top of branch "release-4.15":
In 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/test-infra repository. |
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-node-tuning-operator-container-v4.16.0-202402121340.p0.g836b327.assembly.stream.el9 for distgit cluster-node-tuning-operator. |
* e2e: allowed annotation to ns The the allowed mixedcpus annotation to the testing namespace. Without the annotation the api admission pliugin will reject the request for the workload creation. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: mixedcpus: add e2e tests 1. Basic test to verify that pod which asks for shared cpus, has the shared cpus under its cgroup cpuset. 2. Check that `cpu-quota.crio.io: disable` annotation works along with mixedcpus. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: check env variable exsitance Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: cancel SMT alignment On some environments we have very few resources. On order to be able to run tests on those type of environment, we must narrow down the resources required by the test pod, but yet keep their guaranteed QoS class. This means that one is the minimal possible, but the pod will failed with SMT alignment error, hence in such cases we want to cancel the SMT alignment. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: test updates to shared cpus under profile This test changes the shared cpuset under the profile, wait for mcp to catchup, and checks if the container has been updated to reflect the new shared cpuset. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: use `mustParse` Use `mustParse` to make sure we assert in case of invalid cpuset string Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: fix controller file naming The controller file names on cgroupv1 are different than the one on cgroupv2. This is a pure copy-paste mistake. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: addressed reviewers comments * Check the len returned from split * Use `GinkgoHelper()` Signed-off-by: Talor Itzhak <titzhak@redhat.com> --------- Signed-off-by: Talor Itzhak <titzhak@redhat.com>
* CNF-9173: e2e: mixedcpus test (#892) * e2e: allowed annotation to ns The the allowed mixedcpus annotation to the testing namespace. Without the annotation the api admission pliugin will reject the request for the workload creation. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: mixedcpus: add e2e tests 1. Basic test to verify that pod which asks for shared cpus, has the shared cpus under its cgroup cpuset. 2. Check that `cpu-quota.crio.io: disable` annotation works along with mixedcpus. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: check env variable exsitance Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: cancel SMT alignment On some environments we have very few resources. On order to be able to run tests on those type of environment, we must narrow down the resources required by the test pod, but yet keep their guaranteed QoS class. This means that one is the minimal possible, but the pod will failed with SMT alignment error, hence in such cases we want to cancel the SMT alignment. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: test updates to shared cpus under profile This test changes the shared cpuset under the profile, wait for mcp to catchup, and checks if the container has been updated to reflect the new shared cpuset. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: use `mustParse` Use `mustParse` to make sure we assert in case of invalid cpuset string Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: fix controller file naming The controller file names on cgroupv1 are different than the one on cgroupv2. This is a pure copy-paste mistake. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: addressed reviewers comments * Check the len returned from split * Use `GinkgoHelper()` Signed-off-by: Talor Itzhak <titzhak@redhat.com> --------- Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: check if shared CPUs survive Kubelet restart Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: remove ctx arg Leftovers from the cherry-pick which was done from 4.16. On 4.16 we already updated most of our functions to accept context as the first argument. On 4.15 we don't, hence we shall remove it. Signed-off-by: Talor Itzhak <titzhak@redhat.com> * e2e: `UpdateWithRetry` only update spec The function contains a subtle bug on which the update is done only for fileds under the `Spec` This means that changes to annotations and labels field outside the `Spec` won't take affect. Signed-off-by: Talor Itzhak <titzhak@redhat.com> --------- Signed-off-by: Talor Itzhak <titzhak@redhat.com>
This is a first PR (more to come) that tests the mixed-cpus e2e.
It contains the following tests:
Basic test to verify that pod which asks for shared cpus, has the shared cpus under
its cgroup cpuset.
Check that
cpu-quota.crio.io: disable
annotation works along with mixedcpus.Check that
OPENSHIFT_ISOLATED_CPUS
andOPENSHIFT_SHARED_CPUS
env variables are under the container and configured properly.Verify that updates to shared CPUs under the profile are reflect under the containers correctly.