-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
node e2e: fix CPUManager related jobs. #30545
Conversation
I have verified on my environment using:
Here is the tailed output:
And below is the information of
|
Added in #29717 |
/test pull-kubernetes-node-kubelet-serial-cpu-manager-kubetest2 |
@bart0sh: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
/cc |
/cc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR, appreciate you taking the time to look into this.
Currently the config file names seem to indicate that the config is cpu manager specific even though that is not the case. Perhaps we can rename jobs/e2e_node/containerd/image-config-serial-cpu-manager.yaml
and jobs/e2e_node/containerd/ubuntu-init-cpu-manager.yaml
to something more generic so we can use it for testing other components that also need multi-numa test infrastructure.
@swatisehgal Thanks for your review ! How about we create somethings like |
That sounds good. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for this fix! seems fine to me but I must admit I have few gaps I need to close about test-infra config in general. A question inside.
@@ -0,0 +1,13 @@ | |||
#cloud-config |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC this is derived from ubuntu-init-hugepages-1G-allocation.yaml
which in turn seems a fixed and a stripped down version of init.yaml
. Is that the case?
Two followup questions: do we need cni-plugins 0.7.5 or can we use 1.0.1? if we can use 1.0.1, can we just use init.yaml
?
The reason I'm asking is because unless we have clearly different needs (like hugepages has!) I think is best to reuse existing common config and avoid proliferation of lane-specific config if we can help it, to keep the complexity at bay.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
7048729
to
6c70ce2
Compare
thanks for reverting to the |
Use n2d-standard-32 in resource-managers node e2e tests for NUMA-related options. Signed-off-by: Ruquan Zhao <[email protected]>
6c70ce2
to
a36ef93
Compare
Serveral testcases skipped in |
thanks, I think this is fine. I'll review shortly. |
/test pull-test-infra-unit-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold |
/lgtm thanks! |
Also, removing `jobs/e2e_node/image-config-serial-multi-numa.yaml` as it is no longer needed. Follow-up from: test-infra kubernetes/pull/30545 Signed-off-by: Swati Sehgal <[email protected]>
Also, removing `jobs/e2e_node/image-config-serial-multi-numa.yaml` as it is no longer needed. Follow-up from: test-infra kubernetes/pull/30545 Signed-off-by: Swati Sehgal <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ruquanzhao, SergeyKanzhelev, swatisehgal 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 |
@ruquanzhao: Updated the
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. |
This PR fixes failing/not working jobs of CPU manager:
Changes: