-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Open
Labels
kind/flakeCategorizes issue or PR as related to a flaky test.Categorizes issue or PR as related to a flaky test.needs-priorityIndicates an issue lacks a `priority/foo` label and requires one.Indicates an issue lacks a `priority/foo` label and requires one.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Description
Which jobs are flaking?
periodic-cluster-api-e2e-main
Which tests are flaking?
- When testing MachineDeployment rolling upgrades and in-place taint propagation Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
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
Labels
kind/flakeCategorizes issue or PR as related to a flaky test.Categorizes issue or PR as related to a flaky test.needs-priorityIndicates an issue lacks a `priority/foo` label and requires one.Indicates an issue lacks a `priority/foo` label and requires one.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Type
Projects
Status
No status