search

kubernetes-sigs / cluster-api-provider-kubevirt

Cluster API Provider for KubeVirt
Apache License 2.0
110 stars 63 forks source link

clusterctl init failed #223

Closed iming0319 closed 8 months ago

iming0319 commented 1 year ago

What steps did you take and what happened: [A clear and concise description on how to REPRODUCE the bug.] by standard cluster init command $ clusterctl init --infrastructure kubevirt I met error message Error: failed to get provider components for the "kubevirt" provider: failed to read "infrastructure-components.yaml" from provider's repository "infrastructure-kubevirt": failed to get GitHub release v0.1.5: failed to read release "v0.1.5": GET https://api.github.com/repos/kubernetes-sigs/cluster-api-provider-kubevirt/releases/tags/v0.1.5: 404 Not Found []

What did you expect to happen: message "Your management cluster has been initialized successfully"

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] This is because the latest release is 0.1.5 but git hub release stays in 0.1.4 Just release 0.1.5, especially the file "infrastructure-components.yaml"!

Environment:

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

cchengleo commented 1 year ago

There is some issue when cutting the release for 0.1.5. Could you try 0.1.6?

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle rotten

k8s-triage-robot commented 8 months ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 8 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/issues/223#issuecomment-1899352319): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.