哪些任务出现问题?
- e2e-kops-aws-cni-cilium-eni
- ci-kubernetes-kind-e2e-parallel-1-29
- pull-kubernetes-e2e-kind
哪些测试出现问题?
Kubernetes e2e套件:[It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] read-write-once-pod [MinimumKubeletVersion:1.27] 应该阻止同一节点上的第二个Pod使用正在使用的ReadWriteOncePod卷
自何时以来出现问题?
不清楚。似乎已经持续了一段时间,但我还没有找到已经提交的问题。
https://storage.googleapis.com/k8s-triage/index.html?date=2024-05-09&test=should%20block%20a%20second%20pod%20from%20using%20an%20in-use%20ReadWriteOncePod
Testgrid链接
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-e2e-kind
失败原因(如果可能)
[FAILED] failed to wait for FailedMount event for pod2: got error while getting events: client rate limiter Wait returned an error: context deadline exceeded
In [It] at: k8s.io/kubernetes/test/e2e/storage/testsuites/readwriteoncepod.go:233
[FAILED] failed to wait for FailedMount event for pod2: got error while getting events: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
我们还需要了解什么吗?
相关SIG(s)
/sig storage
3条答案
按热度按时间bfnvny8b1#
仅供参考:我使用GitHub Action在
pull-kubernetes-e2e-kind
上进行了一些测试,如果PARALLEL=false
,那么总是成功的。只有在PARALLEL为true时,问题才能被重现。nbysray52#
OutOfpods: 节点没有足够的资源:pods,请求:1,已使用:110,容量:110
kse8i1jr3#
/triage accepted