Skip to content

[Failing test][cluster-api-core-main] invalid ControlPlane upgrade plan: control plane upgrade plan must end with version v1.35.0-alpha.0.712+f8f1e49f3b1288 #12774

@wendy-ha18

Description

@wendy-ha18

Which jobs are failing?

cluster-api-core-main

  • capi-e2e-latestk8s-main

Which tests are failing?

capi-e2e.[It] When performing chained upgrades for workload cluster using ClusterClass in a different NS with RuntimeSDK [ClusterClass] Should create, upgrade and delete a workload cluster [ClusterClass].

Prow
Triage

Since when has it been failing?

According to Triage, this test started to fail since 13 September.

This is Prow logs of 3 recents run:

16/09/2025, 13:52:51
16/09/2025, 10:47:58
16/09/2025, 07:47:59

Testgrid link

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

Reason for failure (if possible)

{Failed to default and validate the upgrade plan
Unexpected error:
    <*errors.fundamental | 0xc000f086f0>: 
    invalid ControlPlane upgrade plan: control plane upgrade plan must end with version v1.35.0-alpha.0.712+f8f1e49f3b1288, ends with v1.34.0 instead
    {
        msg: "invalid ControlPlane upgrade plan: control plane upgrade plan must end with version v1.35.0-alpha.0.712+f8f1e49f3b1288, ends with v1.34.0 instead",
        stack: [0x248ab6a, 0x251bc97, 0x897ff3, 0x8aca13, 0x484341],
    }
occurred failed [FAILED] Failed to default and validate the upgrade plan
Unexpected error:
    <*errors.fundamental | 0xc000f086f0>: 
    invalid ControlPlane upgrade plan: control plane upgrade plan must end with version v1.35.0-alpha.0.712+f8f1e49f3b1288, ends with v1.34.0 instead
    {
        msg: "invalid ControlPlane upgrade plan: control plane upgrade plan must end with version v1.35.0-alpha.0.712+f8f1e49f3b1288, ends with v1.34.0 instead",
        stack: [0x248ab6a, 0x251bc97, 0x897ff3, 0x8aca13, 0x484341],
    }
occurred
In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api/test/e2e/cluster_upgrade_runtimesdk.go:285 @ 09/16/25 07:39:31.35

There were additional failures detected after the initial failure. These are visible in the timeline
}

Anything else we need to know?

No response

Label(s) to be applied

/kind failing-test
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/failing-testCategorizes issue or PR as related to a consistently or frequently failing 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