github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-08 03:33:56 +00:00
Code Issues Projects Releases Wiki Activity

fix limitrange flaky test

Browse Source
This commit is contained in:
carlory 2023-10-12 18:58:37 +08:00
parent 963178207a
commit a34d2f3b13
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
test/e2e/scheduling/limit_range.go
View File

@ -223,7 +223,20 @@ var _ = SIGDescribe("LimitRange", func() {
ginkgo.By("Creating a Pod with more than former max resources")
pod = newTestPod(podName+"2", getResourceList("600m", "600Mi", "600Gi"), v1.ResourceList{})
_, err = f.ClientSet.CoreV1().Pods(f.Namespace.Name).Create(ctx, pod, metav1.CreateOptions{})
// When the LimitRanger admission plugin find 0 items from the LimitRange informer cache,
// it will try to lookup LimitRanges from the local LiveLookupCache which liveTTL is 30s.
// If a LimitRange was deleted from the apiserver, informer watch the delete event and then
// handle it lead to the informer cache doesn't have any other items, but the local LiveLookupCache
// has it and not expired at the same time, the LimitRanger admission plugin will use the
// deleted LimitRange to validate the request. So the request will be rejected by the plugin
// till the item is expired.
//
// With the following retry, we can make sure the item is expired and the request will be
// validated as expected.
err = framework.Gomega().Eventually(ctx, func(ctx context.Context) error {
_, err = f.ClientSet.CoreV1().Pods(f.Namespace.Name).Create(ctx, pod, metav1.CreateOptions{})
return err
}).WithPolling(5 * time.Second).WithTimeout(30 * time.Second).ShouldNot(gomega.HaveOccurred())
framework.ExpectNoError(err)
})