Skip to content
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

Enable running cpu-mgr-multiNUMA e2e tests with Topology manager #88566

Merged

Conversation

Deepthidharwar
Copy link
Contributor

@Deepthidharwar Deepthidharwar commented Feb 26, 2020

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind cleanup

What this PR does / why we need it:
Currently, TopologyManager e2e tests have a copy of CPU Manager e2e test code and does not support MultiNUMA support. This PR addresses both these issues by code-refactor and re-use.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Feb 26, 2020
@k8s-ci-robot
Copy link
Contributor

Hi @Deepthidharwar. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. area/test sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 26, 2020
@Deepthidharwar
Copy link
Contributor Author

@vpickard @ConnorDoyle , @fromanirh , Please do review and if it looks ok, need ok-to-test.

@Deepthidharwar
Copy link
Contributor Author

/test pull-kubernetes-node-kubelet-serial-cpu-manager

@k8s-ci-robot
Copy link
Contributor

@Deepthidharwar: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test pull-kubernetes-node-kubelet-serial-cpu-manager

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.

@nolancon
Copy link

/ok-to-test

1 similar comment
@nolancon
Copy link

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 27, 2020
@nolancon
Copy link

/test pull-kubernetes-node-e2e-containerd

@vpickard
Copy link
Contributor

vpickard commented Feb 27, 2020

/test pull-kubernetes-node-e2e-containerd

It looks like this test is failing consistently across the board. I have posted a message on #sig-testing to see if the test env needs some tidying up. For reference, here is a link to this job run history:

https://prow.k8s.io/job-history/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-node-e2e-containerd

And here is the failure:

I0227 18:48:05.570] unable to create gce instance with running docker daemon for image cos-73-11647-459-0. could not create instance tmp-node-e2e-0a7f6c8e-cos-73-11647-459-0: [&{Code:QUOTA_EXCEEDED Location: Message:Quota 'IN_USE_ADDRESSES' exceeded. Limit: 69.0 in region us-west1. ForceSendFields:[] NullFields:[]}]

@Deepthidharwar
Copy link
Contributor Author

/retest

@Deepthidharwar
Copy link
Contributor Author

/test pull-kubernetes-node-kubelet-serial-cpu-manager

@vpickard
Copy link
Contributor

/test pull-kubernetes-node-kubelet-serial-topology-manager

@Deepthidharwar
Copy link
Contributor Author

Deepthidharwar commented Feb 28, 2020

Failing test is not cpu-manager's test but SR-IOV device plugin tests. Looking into this.

@ffromani
Copy link
Contributor

ffromani commented Feb 28, 2020

Failing test is not cpu-manager's test but SR-IOV device plugin tests. Looking into this.

It's a bug I introduced in the tests which triggers when the tests are run on a box without any SRIOV device. The logic which tries to detect if we need to skip the tests for this very reason is flawed.

@Deepthidharwar
Copy link
Contributor Author

@fromanirh , SRIOV detection logic is reporting error on systems that does not have one enabled https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/topology_manager_test.go#L172 . This should not error out.

@ffromani
Copy link
Contributor

ffromani commented Feb 28, 2020

@fromanirh , SRIOV detection logic is reporting error on systems that does not have one enabled https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/topology_manager_test.go#L172 . This should not error out.

Correct. It should read like

if len(pciPerNuma) == 0 {
   return -1, false
}

The code as it is is correct in the flow the tests I added are using. Changing like I wrote above make it work in the general flow.
Sorry for this bug.

@Deepthidharwar
Copy link
Contributor Author

#88721 has the fix for this as discussed above.

@Deepthidharwar
Copy link
Contributor Author

The changes made as part of this patch runs fine on systems with fix in #88721.

Copy link
Contributor

@ffromani ffromani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm assuming the inline comment is handled

e2eskipper.Skipf("Skipping CPU Manager tests since the CPU capacity < 2")
}
ginkgo.By("by deleting the pods and waiting for container removal")
deletePods(f, []string{pod.Name})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I'm not mistaken, the original code had

waitForContainerRemoval(pod.Spec.Containers[0].Name, pod.Name, pod.Namespace)

here. If so, I'd add it again.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch.

…er-e2e-testsuite.

Signed-off-by: Deepthi Dharwar <ddharwar@redhat.com>
Signed-off-by: Deepthi Dharwar <ddharwar@redhat.com>
@Deepthidharwar
Copy link
Contributor Author

/retest

@ffromani
Copy link
Contributor

ffromani commented Mar 2, 2020

lgtm now. Thanks for the updates!

@rphillips
Copy link
Member

/lgtm
/assign @derekwaynecarr

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2020
@derekwaynecarr
Copy link
Member

the refactoring was clean. thanks for the follow-up.

/approve
/lgtm

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Deepthidharwar, derekwaynecarr

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 5, 2020
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Mar 5, 2020
@Deepthidharwar
Copy link
Contributor Author

/kind cleanup

@Deepthidharwar
Copy link
Contributor Author

/retest

1 similar comment
@Deepthidharwar
Copy link
Contributor Author

/retest

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 5, 2020

@Deepthidharwar: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-kubernetes-node-kubelet-serial-topology-manager ebb3bdc023bed37f770aaa9f640757118b2a45e3 link /test pull-kubernetes-node-kubelet-serial-topology-manager

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@nolancon
Copy link

nolancon commented Mar 5, 2020

/test pull-kubernetes-e2e-gce

@k8s-ci-robot k8s-ci-robot merged commit 1f2e196 into kubernetes:master Mar 5, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants