Skip to content

[Flaking Test] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls #132201

Open
@adilGhaffarDev

Description

@adilGhaffarDev

Which jobs are flaking?

master-blocking

  • ci-crio-cgroupv2-node-e2e-conformance
  • ci-crio-cgroupv1-node-e2e-conformance

Which tests are flaking?

The following tests are flaking with the same error:

  • E2eNode Suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls with slashes as separator [MinimumKubeletVersion:1.23] [Environment:NotInUserNS]
  • E2eNode Suite [It] [sig-node] Sysctls [LinuxOnly] [NodeConformance] should support sysctls [MinimumKubeletVersion:1.21] [Environment:NotInUserNS] [Conformance]

Triage
Prow

Since when has it been flaking?

09/06/2025, 04:22:33
08/06/2025, 10:20:36
08/06/2025, 06:19:38
08/06/2025, 13:04:37
07/06/2025, 21:14:35
06/06/2025, 18:07:32

Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#ci-crio-cgroupv2-node-e2e-conformance

Reason for failure (if possible)

[FAILED] Expected
    <*v1.Event | 0xc00144ac88>: 
        count: 1
        eventTime: null
        firstTimestamp: "2025-05-28T22:58:47Z"
        involvedObject:
          apiVersion: v1
          fieldPath: spec.containers{test-container}
          kind: Pod
          name: sysctl-3366d96d-1de1-4477-bcac-180b90cb8c47
          namespace: sysctl-4574
          resourceVersion: "97"
          uid: 1dcfafcf-b994-4d78-899d-a6aa5fbda208
        lastTimestamp: "2025-05-28T22:58:47Z"
        message: 'Error: error reading from server: read unix @->/var/run/crio/crio.sock:
          read: connection reset by peer'
        metadata:
          creationTimestamp: "2025-05-28T22:58:47Z"
          managedFields:
          - apiVersion: v1
            fieldsType: FieldsV1
            fieldsV1:
              f:count: {}
              f:firstTimestamp: {}
              f:involvedObject: {}
              f:lastTimestamp: {}
              f:message: {}
              f:reason: {}
              f:reportingComponent: {}
              f:reportingInstance: {}
              f:source:
                f:component: {}
                f:host: {}
              f:type: {}
            manager: kubelet
            operation: Update
            time: "2025-05-28T22:58:47Z"
          name: sysctl-3366d96d-1de1-4477-bcac-180b90cb8c47.1843d30bb163afa3
          namespace: sysctl-4574
          resourceVersion: "126"
          uid: acddd398-eaba-4f67-bc04-bbb3b26d5723
        reason: Failed
        reportingComponent: kubelet
        reportingInstance: tmp-node-e2e-5ee183ac-fedora-coreos-42-20250512-3-0-gcp-x86-64
        source:
          component: kubelet
          host: tmp-node-e2e-5ee183ac-fedora-coreos-42-20250512-3-0-gcp-x86-64
        type: Warning
to be nil
In [It] at: k8s.io/kubernetes/test/e2e/common/node/sysctl.go:210 @ 05/28/25 22:58:48.004

Anything else we need to know?

No response

Relevant SIG(s)

/sig node

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/flakeCategorizes issue or PR as related to a flaky test.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/nodeCategorizes an issue or PR as relevant to SIG Node.

    Type

    No type

    Projects

    Status

    FLAKY

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions