-
Notifications
You must be signed in to change notification settings - Fork 253
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
🌱 Bump CAPI to v1.8.1 #2154
🌱 Bump CAPI to v1.8.1 #2154
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/test pull-cluster-api-provider-openstack-e2e-full-test |
changes ok so only need fix those test errors
|
bbce98e
to
75465d5
Compare
/test pull-cluster-api-provider-openstack-e2e-full-test |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/test pull-cluster-api-provider-openstack-e2e-full-test |
@mdbooth ready for review, but with your PTO you might not have time to review it today. I guess this can wait. |
@pierreprinetti hey, I had to rebase this one today. I could use an extra pair of eyes in case I rebased something wrong. |
/test pull-cluster-api-provider-openstack-e2e-full-test |
This is ready to go but it won't pass the upgrade tests until we got #2156 merged. |
They are in CAPI now, we import them.
/test pull-cluster-api-provider-openstack-e2e-full-test |
1 similar comment
/test pull-cluster-api-provider-openstack-e2e-full-test |
Pretty sure the error is here:
Guessing this is either new, or wasn't previously checked. |
/test pull-cluster-api-provider-openstack-e2e-full-test |
/test pull-cluster-api-provider-openstack-e2e-full-test |
1 similar comment
/test pull-cluster-api-provider-openstack-e2e-full-test |
I think we've been caught out by kubernetes-sigs/cluster-api#10609. Before this change the test was implicity using the value of Incidentally this change landed in CAPI v1.8.0, so I suspect we didn't run this test before landing that bump 😬 Edit: |
/test pull-cluster-api-provider-openstack-e2e-full-test |
@EmilienM We'll want to do some squashing on this PR before merging. Maybe not all the commits, but we should squash as many commits as it ends up taking to fix the upgrade test. |
…Input` As we are only interested in testing a CAPO upgrade, this should stay in sync with the k8s version used in other tests.
/test pull-cluster-api-provider-openstack-e2e-full-test |
/lgtm @EmilienM Suggest you self-approve this. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EmilienM 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 |
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 #2144
Co-Authored-By: @mdbooth