Skip to content

[e2e] When testing MachineDeployment rolling upgrades and in-place taint propagation is failing #13008

@arshadd-b

Description

@arshadd-b

Which jobs are flaking?

periodic-cluster-api-e2e-main

Which tests are flaking?

  1. When testing MachineDeployment rolling upgrades and in-place taint propagation Should successfully upgrade Machines upon changes in relevant MachineDeployment fields

dashboard link: https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=.*cluster-api.*e2e.*main&test=When%20testing%20MachineDeployment%20rolling%20upgrades%20and%20in-place%20taint%20propagation%20&xjob=.*-provider-

Since when has it been flaking?

could see failure from 15/11/2025
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/periodic-cluster-api-e2e-main/1989612616221200384

Testgrid link

https://testgrid.k8s.io/cluster-api-core-main#capi-e2e-main

Reason for failure (if possible)

Machines must not be replaced through in-place rollout
Expected
    <bool>: false
to be true
[FAILED] Failed after 0.018s.
The function passed to Consistently failed at /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/md_rollout.go:280 with:
Machines must not be replaced through in-place rollout
Expected
    <bool>: false
to be true

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

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions