clusterctl init doesn't work when metadata is merged but release isn't published #4633
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
/kind bug
[Before submitting an issue, have you checked the Troubleshooting Guide?]
What steps did you take and what happened:
According to the release instructions, we first merge the metadata for the release and then publish it. However, this ends up breaking clusterctl init between when we merge the metadata and before the release is actually published.
Running:
Gives this error:
This also affects specifying a specific version when running
clusterctl init
, so nobody is able to initialize a management cluster during this period.What did you expect to happen:
clusterctl init --infrastructure azure
should always work.Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: