Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

While performing clusterctl upgrade plan it failed with Error: invalid provider metadata: version v0.3.0 #355

Open
NinitLtd opened this issue Jan 31, 2025 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@NinitLtd
Copy link

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
I'm trying to perform clusterctl upgrade plan on one of my existing management cluster. The plan was working fine couple of days back but now its failing with following error.

Checking new release availability...
Error: invalid provider metadata: version v0.3.0 (one of the available versions) for the provider caaph-system/addon-helm does not match any release series

What did you expect to happen:

I was expecting a list of providers which will need upgrade on the management cluster.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

It looks like there is a pending Pull request for this change
https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/pull/354/files

Environment:

  • Cluster API version: 1.8.5 and 1.9.4
  • Cluster API Add-on Provider for Helm version: 0.2.6
  • minikube/kind version:
  • Kubernetes version: (use kubectl version): v1.31.4
  • OS (e.g. from /etc/os-release):

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants