kubernetes [Flaking Test] [sig-node] CriticalPod [Serial] [Disruptive] [NodeFeature:CriticalPod] 当我们需要接受一个关键的pod时,应该...

krcsximq  于 9个月前  发布在  Kubernetes
关注(0)|答案(3)|浏览(102)

实际上,有两个不稳定的测试

  • [sig-node] 当我们需要接受一个关键Pod时,应该能够创建和删除关键Pod的严重Pod[Serial] [Disruptive] [NodeFeature:CriticalPod]
  • 长时间不崩溃 [sig-node] 当我们需要接受一个关键Pod时,应该将DisruptionTarget条件添加到被抢占的pod中[NodeFeature:PodDisruptionConditions]

这两个都在https://testgrid.k8s.io/sig-node-release-blocking#node-kubelet-serial-containerd中出现了不稳定。一些相关的旧问题是

故障集群 380df937894e999e459f

错误文本:

E2eNode Suite [It] [sig-node] 当我们需要接受一个关键Pod时,应该能够创建和删除关键Pod的严重Pod[Serial] [Disruptive] [NodeFeature:CriticalPod]

  1. [FAILED] Told to stop trying after 2.004s.
  2. The phase of Pod static-critical-pod is Failed which is unexpected.
  3. In [It] at: k8s.io/kubernetes/test/e2e/framework/pod/pod_client.go:106 @ 03/05/24 09:14:59.881

E2eNode Suite [It] [sig-node] 当我们需要接受一个关键Pod时,应该将DisruptionTarget条件添加到被抢占的pod中[NodeFeature:PodDisruptionConditions]

  1. status:
  2. message: 'Pod was rejected: Unexpected error while attempting to recover from admission
  3. failure: preemption: error finding a set of pods to preempt: no set of running
  4. pods found to reclaim resources: [(res: memory, q: 15728640), ]'
  5. phase: Failed
  6. reason: UnexpectedAdmissionError
  7. startTime: "2024-03-09T11:55:48Z"
最近的故障:

2024/3/14 03:01:15 ci-cgroupv2-containerd-node-arm64-al2023-e2e-serial-ec2-eks
2024/3/10 20:55:56 ci-cgroupv2-containerd-node-e2e-serial-ec2
2024/3/10 20:32:43 ci-kubernetes-node-swap-fedora-serial
2024/3/10 02:54:57 ci-cgroupv2-containerd-node-arm64-e2e-serial-ec2
2024/3/8 21:49:09 ci-kubernetes-node-kubelet-serial-containerd
/kind flake
/sig node

slsn1g29

slsn1g291#

/cc @saschagrunert@ruiwen-zhao@ffromani
谁正在处理之前的故障/失败。

nxowjjhe

nxowjjhe2#

/triage已接受
我认为这个故障已经相当老了:[sig-node] CriticalPod [Serial] [Disruptive] [NodeFeature:CriticalPod] when we need to admit a critical pod should be able to create and delete a critical pod
我不确定第二个([sig-node] CriticalPod [Serial] [Disruptive] [NodeFeature:CriticalPod] when we need to admit a critical pod should add DisruptionTarget condition to the preempted pod [NodeFeature:PodDisruptionConditions])是否与之相关。
我可能会在接下来的几周内抽出时间来研究这个问题👍

qojgxg4l

qojgxg4l3#

我认为这个片子很旧:[sig-node] CriticalPod [Serial] [Disruptive] [NodeFeature:CriticalPod] when we need to admit a critical pod should be able to create and delete a critical pod
这个旧片子仍然在起作用
我不确定第二个([sig-node] CriticalPod [Serial] [Disruptive] [NodeFeature:CriticalPod] when we need to admit a critical pod should add DisruptionTarget condition to the preempted pod [NodeFeature:PodDisruptionConditions])是否与那个有关。
这个片子最近没有起作用。

相关问题