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
update cluster-api to 0.3.9 #639
update cluster-api to 0.3.9 #639
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Build failed.
|
@jichenjc CAPI v0.3.10 is due for release this month end or early Oct. Whatever you think might work the best :) |
0eb4980
to
497e13f
Compare
@prankul88 thanks for the comments, updated |
/test pull-cluster-api-provider-openstack-test |
@jichenjc Looks good. Let's wait for the tests 👍 |
497e13f
to
e0c3e7c
Compare
Sorry didnt see the tests already failed. Will check this in my local. |
e0c3e7c
to
dd1163e
Compare
Build failed.
|
recheck |
@prankul88 I think the previous failed test pass now :) |
Build failed.
|
recheck |
@prankul88 please help to check again :) |
Build failed.
|
recheck |
Build failed.
|
recheck |
Build failed.
|
2cf729f
to
b2ad7dc
Compare
Build failed.
|
b2ad7dc
to
461731d
Compare
Build failed.
|
461731d
to
be04285
Compare
Build failed.
|
be04285
to
0249ec6
Compare
Build failed.
|
0249ec6
to
f113917
Compare
Build failed.
|
Makefile
Outdated
@@ -335,7 +337,7 @@ create-cluster: $(CLUSTERCTL) $(KUSTOMIZE) $(ENVSUBST) ## Create a development K | |||
|
|||
# (Re-)install Core providers | |||
$(CLUSTERCTL) delete --all | |||
$(CLUSTERCTL) init --core cluster-api:v0.3.8 --bootstrap kubeadm:v0.3.8 --control-plane kubeadm:v0.3.8 | |||
$(CLUSTERCTL) init --core cluster-api:v${CAPI_VERSION} --bootstrap kubeadm:v${CAPI_VERSION} --control-plane kubeadm:v${CAPI_VERSION} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we may be able to avoid the latest acceptance-test error by combining l340 and l345 into l345.
$(CLUSTERCTL) init --config ./out/clusterctl.yaml --infrastructure openstack --core cluster-api:v${CAPI_VERSION} --bootstrap kubeadm:v${CAPI_VERSION} --control-plane kubeadm:v${CAPI_VERSION}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure... let's give a try :)
recheck |
Build failed.
|
recheck |
Build failed.
|
f113917
to
f3ec7b4
Compare
Build failed.
|
recheck |
Build failed.
|
recheck |
Build failed.
|
recheck |
Build succeeded.
|
@hidekazuna can you help to merge this ? |
/lgtm Though CAPI v0.3.10 has been already released. |
@hidekazuna I will push a patch for capi v0.3.10 |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: