Skip to content

Error: failed to parse next version for capi-kubeadm-bootstrap-system/bootstrap-kubeadm provider: strconv.ParseUint: parsing "": invalid syntax #12751

@Breee

Description

@Breee

What steps did you take and what happened?

If I execute clusterctl upgrade plan it shows everything that would be updated:

$ clusterctl upgrade plan <Cluster>
v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
Checking if cert-manager needs upgrade...
Cert-Manager is already up to date
Checking new release availability...
Latest release available for the v1beta2 Cluster API contract version:
NAME                     NAMESPACE                           TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm        capi-kubeadm-bootstrap-system       BootstrapProvider        v1.11.1           Already up to date
control-plane-kubeadm    capi-kubeadm-control-plane-system   ControlPlaneProvider     v1.11.1           Already up to date
cluster-api              capi-system                         CoreProvider             v1.11.1           Already up to date
infrastructure-vsphere   capv-system                         InfrastructureProvider   v1.14.0           Already up to date
You are already up to date!

When i then try to upgrade:

$ clusterctl upgrade apply --contract v1beta2 --wait-providers --wait-provider-timeout 600
v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
Checking if cert-manager needs upgrade...
Cert-manager is already up to date
Performing upgrade...
Error: failed to parse next version for capi-kubeadm-bootstrap-system/bootstrap-kubeadm provider: strconv.ParseUint: parsing "": invalid syntax

Current workaround:

clusterctl upgrade apply --bootstrap kubeadm:v1.11.1  --control-plane kubeadm:v1.11.1 --core cluster-api:v1.11.1 --infrastructure vsphere:v1.14.0`

Any ideas`?

What did you expect to happen?

That it just updates/does nothing because it is up to date.

Cluster API version

v1.11.1

Kubernetes version

No response

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
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/bugCategorizes issue or PR as related to a bug.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