kubernetes [Flaking] [sig-node] 当创建一个镜像pod时，如果没有更改，当文件被删除并重新创建时，MirrorPod应该成功地重新创建,[NodeConformance]

czfnxgou 于 4个月前发布在 Kubernetes

关注(0)|答案(6)|浏览(76)

哪些工作出现问题？

https://storage.googleapis.com/k8s-triage/index.html?test=MirrorPod%20when%20create%20a%20mirror%20pod%20without%20changes
[sig-node] 在没有更改的情况下创建镜像Pod时，当文件被删除并重新创建时，MirrorPod应该成功地重新创建 [NodeConformance]

哪些测试出现问题？

[FAILED] Timed out after 120.001s.
Expected
    <*fmt.wrapError | 0xc0006eeda0>: 
    expected the mirror pod "graceful-pod-1fd4f565-732f-4cac-9504-69b5e487b375-tmp-node-e2e-b221d0d6-fedora-coreos-38-20231027-3-2-gcp-x86-64" to appear: pods "graceful-pod-1fd4f565-732f-4cac-9504-69b5e487b375-tmp-node-e2e-b221d0d6-fedora-coreos-38-20231027-3-2-gcp-x86-64" not found
    {
        msg: "expected the mirror pod \"graceful-pod-1fd4f565-732f-4cac-9504-69b5e487b375-tmp-node-e2e-b221d0d6-fedora-coreos-38-20231027-3-2-gcp-x86-64\" to appear: pods \"graceful-pod-1fd4f565-732f-4cac-9504-69b5e487b375-tmp-node-e2e-b221d0d6-fedora-coreos-38-20231027-3-2-gcp-x86-64\" not found",
        err: <*errors.StatusError | 0xc0008880a0>{
            ErrStatus: {
                TypeMeta: {Kind: "", APIVersion: ""},
                ListMeta: {
                    SelfLink: "",
                    ResourceVersion: "",
                    Continue: "",
                    RemainingItemCount: nil,
                },
                Status: "Failure",
                Message: "pods \"graceful-pod-1fd4f565-732f-4cac-9504-69b5e487b375-tmp-node-e2e-b221d0d6-fedora-coreos-38-20231027-3-2-gcp-x86-64\" not found",
                Reason: "NotFound",
                Details: {
                    Name: "graceful-pod-1fd4f565-732f-4cac-9504-69b5e487b375-tmp-node-e2e-b221d0d6-fedora-coreos-38-20231027-3-2-gcp-x86-64",
                    Group: "",
                    Kind: "pods",
                    UID: "",
                    Causes: nil,
                    RetryAfterSeconds: 0,
                },
                Code: 404,
            },
        },
    }
to be nil
In [BeforeEach] at: test/e2e_node/mirror_pod_grace_period_test.go:60 @ 11/18/23 19:19:43.832

从何时开始出现问题？

Testgrid链接

https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv1-evented-pleg
https://testgrid.k8s.io/sig-release-master-informing#ci-crio-cgroupv2-node-e2e-conformance

失败原因(如果可能)

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-crio-cgroupv1-evented-pleg/1729257505558630400

我们还需要了解其他信息吗？

它可能与 #121349 有关。相关功能是 kubernetes/enhancements#3386
在我们将EventedPLEG还原为alpha版本后，它仍然在 ci-crio-cgroupv2-node-e2e-conformance 中出现问题

6条答案

按热度按时间

ej83mcc01#

这个问题目前正在等待分类。
如果SIG或子项目确定这是一个相关的问题，他们将通过应用triage/accepted标签并提供进一步的指导来接受它。
组织成员可以通过在评论中写入/triage accepted来添加triage/accepted标签。
有关使用PR评论与我互动的说明，请查看here。如果您对我的行为有任何问题或建议，请针对kubernetes/test-infra仓库提出一个问题。

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

tpxzln5u2#

STEP: mirror pod should restart with count 1 - k8s.io/kubernetes/test/e2e_node/mirror_pod_test.go:180 @ 01/23/24 20:07:57.962
[FAILED] Timed out after 126.004s.
Expected
    <*fmt.wrapError | 0xc000a92ce0>: 
    expected the mirror pod "static-pod-f493ee91-48e0-4ead-a779-7984c9c9caaa-tmp-node-e2e-bc68fd6f-fedora-coreos-39-20240104-3-0-gcp-x86-64" to appear: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
    {
        msg: "expected the mirror pod \"static-pod-f493ee91-48e0-4ead-a779-7984c9c9caaa-tmp-node-e2e-bc68fd6f-fedora-coreos-39-20240104-3-0-gcp-x86-64\" to appear: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline",
        err: <*fmt.wrapError | 0xc000a92cc0>{
            msg: "client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline",
            err: <*errors.errorString | 0xc000815a00>{
                s: "rate: Wait(n=1) would exceed context deadline",
            },
        },
    }
to be nil

顺便说一下，静态pod在几秒钟后变为运行状态(在最近的不稳定CI中为2-5秒)。

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

dsf9zpds3#

flake once in https://testgrid.k8s.io/sig-release-master-informing#ci-crio-cgroupv1-node-e2e-conformance
/cc @harche@SergeyKanzhelev

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

fzwojiic4#

/assign @harche@rphillips

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

thtygnil5#

我并没有在最近的运行中看到测试出现问题，可以参考这个链接：https://testgrid.k8s.io/sig-release-master-informing#ci-crio-cgroupv2-node-e2e-conformance

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

ejk8hzay6#