[e2e] Error: ResourceVersions didn't stay stable

[peppi-lotta]

Which jobs are flaking?

• periodic-cluster-api-e2e-mink8s-release-1-11
• periodic-cluster-api-e2e-release-1-11

Which tests are flaking?

• capi-e2e [It] When following the Cluster API quick-start with v1beta1 ClusterClass [ClusterClass] Should create a workload cluster [ClusterClass]
• capi-e2e [It] When upgrading a workload cluster using ClusterClass in a different NS with RuntimeSDK [ClusterClass] Should create, upgrade and delete a workload cluster [ClusterClass]
• capi-e2e [It] When following the Cluster API quick-start Should create a workload cluster
• capi-e2e [It] When upgrading a workload cluster using ClusterClass in a different NS with RuntimeSDK [ClusterClass] Should create, upgrade and delete a workload cluster [ClusterClass]

Since when has it been flaking?

Jan 7 2026

Testgrid link

This link shows result where error message contains "ResourceVersions didn't stay stable ":
https://storage.googleapis.com/k8s-triage/index.html?text=resourceVersions%20didn%27t%20stay%20stable

This link shows result where error message contains "Detected objects with changed resourceVersion":
https://storage.googleapis.com/k8s-triage/index.html?text=Detected%20objects%20with%20ch[…]ob=.-cluster-api-.&xjob=.-provider-.%7C.-operator-.

Reason for failure (if possible)

This error is the common part. The surrounding error message differs in all fails.
resourceVersions didn't stay stable

Anything else we need to know?

This is mostly happening in release 1.11 tests but a one occurrences also seen in 1.12

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.

[fabriziopandini]

/help

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.