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

Merge pull request #126066 from dims/tzneal-investigate-oom-test-failure-2

Browse Source 
Fix for OOMKiller test consistently failing in EC2 cgroupv1 serial jobs
This commit is contained in:
Kubernetes Prow Robot 2024-07-14 05:45:09 -07:00 committed by GitHub
commit 8182305707
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
test/e2e_node/oomkiller_linux_test.go
View File

@ -113,6 +113,9 @@ func runOomKillerTest(f *framework.Framework, testCase testCase, kubeReservedMem
}
ginkgo.BeforeEach(func() {
// Precautionary check that kubelet is healthy before running the test.
waitForKubeletToStart(context.TODO(), f)
ginkgo.By("setting up the pod to be used in the test")
e2epod.NewPodClient(f).Create(context.TODO(), testCase.podSpec)
})
@ -164,7 +167,8 @@ func getOOMTargetPod(podName string, ctnName string, createContainer func(name s
Name: podName,
},
Spec: v1.PodSpec{
RestartPolicy: v1.RestartPolicyNever,
PriorityClassName: "system-node-critical",
RestartPolicy: v1.RestartPolicyNever,
Containers: []v1.Container{
createContainer(ctnName),
},
@ -268,7 +272,7 @@ func getOOMTargetContainerWithoutLimit(name string) v1.Container {
"sh",
"-c",
// use the dd tool to attempt to allocate huge block of memory which exceeds the node allocatable
"sleep 5 && dd if=/dev/zero of=/dev/null iflag=fullblock count=10 bs=10G",
"sleep 5 && dd if=/dev/zero of=/dev/null iflag=fullblock count=10 bs=1024G",
},
SecurityContext: &v1.SecurityContext{
SeccompProfile: &v1.SeccompProfile{