github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-24 12:15:52 +00:00
Code Issues Projects Releases Wiki Activity

e2e: hugepages: delete test pod after the test

Browse Source 
Current test assumes that test pod is deleted when the test
namespace is deleted. However, namespace deletion is an asynchronous
operation. The pod may still be running and allocating hugepages
resources when next test case creates another pod that requests
the same hugepages resources. This can cause kubelet to fail the test
pod with this kind of error:
  OutOfhugepages-2Mi: Node didn't have enough resource: hugepages-2Mi
  requested: 6291456, used: 6291456, capacity: 10485760

Explicitly deleting test pod should fix this issue.
This commit is contained in:
Ed Bartosh 2021-05-25 16:28:31 +03:00
parent 7229ea343d
commit 38c56883f1
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
test/e2e_node/hugepages_test.go
View File

@ -352,12 +352,15 @@ var _ = SIGDescribe("HugePages [Serial] [Feature:HugePages][NodeSpecialFeature:H
pod := getHugepagesTestPod(f, limits, mounts, volumes)
ginkgo.By("by running a guarantee pod that requests hugepages")
ginkgo.By("by running a test pod that requests hugepages")
testpod = f.PodClient().CreateSync(pod)
})
// we should use JustAfterEach because framework will teardown the client under the AfterEach method
ginkgo.JustAfterEach(func() {
ginkgo.By(fmt.Sprintf("deleting test pod %s", testpod.Name))
f.PodClient().DeleteSync(testpod.Name, metav1.DeleteOptions{}, 2*time.Minute)
releaseHugepages()
ginkgo.By("restarting kubelet to pick up pre-allocated hugepages")