Skip to content

inmemorymachine_controller_test TestReconcileNormalEtcd/create_pod_if_Node_is_ready expand_more #12310

Closed
@adilGhaffarDev

Description

@adilGhaffarDev

Which jobs are flaking?

  • periodic-cluster-api-test-main
  • periodic-cluster-api-test-mink8s-main

triage link: https://storage.googleapis.com/k8s-triage/index.html?job=.*-cluster-api-.*&xjob=.*-provider-.*%7C.*-operator-.*#282ee00bb46c62cbcbab

Error:

{Failed  === RUN   TestReconcileNormalEtcd/create_pod_if_Node_is_ready
I0528 10:41:52.432149   71432 mux.go:340] "Workload cluster listener created" listenerName="foo" address="https://127.0.0.1:21000"
I0528 10:41:54.994721   71432 mux.go:544] "Etcd member added to WorkloadClusterListener" listenerName="foo" address="https://127.0.0.1:21000" podName="etcd-bar1"
    inmemorymachine_controller_test.go:368: 
        Expected
            <bool>: true
        to be false
--- FAIL: TestReconcileNormalEtcd/create_pod_if_Node_is_ready (2.58s)
}

Which tests are flaking?

sigs.k8s.io/cluster-api/test/infrastructure/docker/internal/controllers/backends/inmemory TestReconcileNormalEtcd/create_pod_if_Node_is_ready

Since when has it been flaking?

first failure on triage board is on 20-5-2025
Not sure if it was flaking before that or not

Testgrid link

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/periodic-cluster-api-test-main/1927672924995588096

Reason for failure (if possible)

No response

Anything else we need to know?

No response

Label(s) to be applied

/kind flake
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/flakeCategorizes issue or PR as related to a flaky test.needs-priorityIndicates an issue lacks a `priority/foo` label and requires one.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions