kubernetes [Flaking Test][sig-storage] 应该阻止同一节点上的第二个pod使用正在使用的ReadWriteOncePod卷,

pobjuy32 于 2个月前发布在 Kubernetes

关注(0)|答案(3)|浏览(48)

哪些任务出现问题？

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

我们还需要了解什么吗？

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/124683/pull-kubernetes-e2e-kind/1788664943130710016

3条答案

按热度按时间

bfnvny8b1#

仅供参考：我使用GitHub Action在pull-kubernetes-e2e-kind上进行了一些测试，如果PARALLEL=false,那么总是成功的。只有在PARALLEL为true时，问题才能被重现。

赞(0）回复(0）举报 2个月前

nbysray52#

OutOfpods: 节点没有足够的资源：pods,请求：1,已使用：110,容量：110

STEP: Collecting events from namespace "read-write-once-pod-9757". @ 05/09/24 20:38:51.154
  STEP: Found 10 events. @ 05/09/24 20:38:51.156
  I0509 20:38:51.156989 65982 dump.go:53] At 2024-05-09 20:33:01 +0000 UTC - event for csi-hostpath5v7vm: {persistentvolume-controller } ExternalProvisioning: Waiting for a volume to be created either by the external provisioner 'csi-hostpath-read-write-once-pod-9757' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
  I0509 20:38:51.157008 65982 dump.go:53] At 2024-05-09 20:33:20 +0000 UTC - event for csi-hostpath5v7vm: {csi-hostpath-read-write-once-pod-9757_csi-hostpathplugin-0_b225a3f7-b843-4de0-ac58-61bc09343ab8 } Provisioning: External provisioner is provisioning volume for claim "read-write-once-pod-9757/csi-hostpath5v7vm"
  I0509 20:38:51.157018 65982 dump.go:53] At 2024-05-09 20:33:20 +0000 UTC - event for csi-hostpath5v7vm: {csi-hostpath-read-write-once-pod-9757_csi-hostpathplugin-0_b225a3f7-b843-4de0-ac58-61bc09343ab8 } ProvisioningSucceeded: Successfully provisioned volume pvc-aef51327-f502-4525-89bb-cb3f30838c95
  I0509 20:38:51.157026 65982 dump.go:53] At 2024-05-09 20:33:21 +0000 UTC - event for pod-55dfb4dd-f05e-4776-a8e1-37283232c0ff: {default-scheduler } Scheduled: Successfully assigned read-write-once-pod-9757/pod-55dfb4dd-f05e-4776-a8e1-37283232c0ff to kind-worker
  I0509 20:38:51.157032 65982 dump.go:53] At 2024-05-09 20:33:22 +0000 UTC - event for pod-55dfb4dd-f05e-4776-a8e1-37283232c0ff: {attachdetach-controller } SuccessfulAttachVolume: AttachVolume.Attach succeeded for volume "pvc-aef51327-f502-4525-89bb-cb3f30838c95" 
  I0509 20:38:51.157039 65982 dump.go:53] At 2024-05-09 20:33:40 +0000 UTC - event for pod-55dfb4dd-f05e-4776-a8e1-37283232c0ff: {kubelet kind-worker} Pulled: Container image "registry.k8s.io/e2e-test-images/busybox:1.36.1-1" already present on machine
  I0509 20:38:51.157046 65982 dump.go:53] At 2024-05-09 20:33:40 +0000 UTC - event for pod-55dfb4dd-f05e-4776-a8e1-37283232c0ff: {kubelet kind-worker} Created: Created container write-pod
  I0509 20:38:51.157056 65982 dump.go:53] At 2024-05-09 20:33:42 +0000 UTC - event for pod-55dfb4dd-f05e-4776-a8e1-37283232c0ff: {kubelet kind-worker} Started: Started container write-pod
  I0509 20:38:51.157063 65982 dump.go:53] At 2024-05-09 20:33:44 +0000 UTC - event for pod-da786ea3-645b-4ea1-9f62-51f97220b8be: {kubelet kind-worker} OutOfpods: Node didn't have enough resource: pods, requested: 1, used: 110, capacity: 110
  I0509 20:38:51.157069 65982 dump.go:53] At 2024-05-09 20:38:44 +0000 UTC - event for pod-55dfb4dd-f05e-4776-a8e1-37283232c0ff: {kubelet kind-worker} Killing: Stopping container write-pod

赞(0）回复(0）举报 2个月前

kse8i1jr3#

/triage accepted

赞(0）回复(0）举报 1个月前

我来回答

kubernetes [Flaking Test][sig-storage] 应该阻止同一节点上的第二个pod使用正在使用的ReadWriteOncePod卷,

哪些任务出现问题？

哪些测试出现问题？

自何时以来出现问题？

Testgrid链接

失败原因(如果可能)

我们还需要了解什么吗？

相关SIG(s)

3条答案

相关问题

热门标签

最新问答