Unable to plan upgrade from v0.4.8 to v0.5.0

[fpicot]

/kind bug

Because the metadata.yaml for the release 0.5.0 only reference the 0.5 series, it seems to be impossible to upgrade the Cloudstack provider without using an override.

What steps did you take and what happened:
On a management cluster with cloudstack provider 0.4.8 deployed, I ran clusterctl upgrade plan, which failed with the error :

Error: invalid provider metadata: version v0.4.8 (the current version) for the provider capc-system/infrastructure-cloudstack does not match any release series

What did you expect to happen:
The command to succeed.

Anything else you would like to add:
It is possible to plan the upgrade by creating an override file as follow in ~/.config/cluster-api/overrides/infrastructure-cloudstack/v0.5.0/metadata.yaml

apiVersion: clusterctl.cluster.x-k8s.io/v1alpha3
kind: Metadata
releaseSeries:
  - major: 0
    minor: 5
    contract: v1beta1
  - major: 0
    minor: 4
    contract: v1beta1

With this override file, the upgrade plan succeed :

# clusterctl upgrade plan
Checking if cert-manager needs upgrade...
Cert-Manager will be upgraded from "v1.9.1" to "v1.14.5"

Checking new release availability...

Latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                        NAMESPACE                           TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm           capi-kubeadm-bootstrap-system       BootstrapProvider        v1.3.5            v1.8.5
control-plane-kubeadm       capi-kubeadm-control-plane-system   ControlPlaneProvider     v1.3.5            v1.8.5
cluster-api                 capi-system                         CoreProvider             v1.3.5            v1.8.5
infrastructure-cloudstack   capc-system                         InfrastructureProvider   v0.4.8            v0.5.0

You can now apply the upgrade by executing the following command:

clusterctl upgrade apply --contract v1beta1

Environment:

• Cluster-api-provider-cloudstack version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vishesh92]

@fpicot We are planning for a release soon. I have added this issue to the 0.6 milestone (https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack/milestone/2)

ref: #413

[vishesh92]

/triage accepted