We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/kind bug
What steps did you take and what happened: [A clear and concise description of what the bug is.] https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/master/Makefile#L319 make create-cluster command refer to old CAPO version.
make create-cluster
What did you expect to happen: This should be changed to v0.3.1
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
git rev-parse HEAD
kubectl version
/etc/os-release
The text was updated successfully, but these errors were encountered:
/assign
Sorry, something went wrong.
The directory name must follow the semantic versioning: vX.Y.Z. We are developing master branch so it is OK the name is v9.9.9 for example.
@hidekazuna Sorry I must have missed the conversation.
Ohh okay, got your point. I just saw the PR for the same got merged. Is there something that needs to be changed now? Thanks for helping
@prankul88 It is ok to be merged 😄 I do not know the best.
prankul88
Successfully merging a pull request may close this issue.
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/master/Makefile#L319
make create-cluster
command refer to old CAPO version.What did you expect to happen:
This should be changed to v0.3.1
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
git rev-parse HEAD
if manually built):kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: