-
Notifications
You must be signed in to change notification settings - Fork 434
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
[WIP] Upgrade CAPI to 1.9.3 #5369
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f092059
to
2895866
Compare
/retest |
/assign |
We might be seeing the same error here as we see in #5368 |
/test pull-cluster-api-provider-azure-apiversion-upgrade |
c96533e
to
86a4ff7
Compare
/test |
@nawazkh: The
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-cluster-api-provider-azure-apiversion-upgrade |
1 similar comment
/test pull-cluster-api-provider-azure-apiversion-upgrade |
- revert using nhk fork of CAPI
074b82c
to
685682f
Compare
/test pull-cluster-api-provider-azure-apiversion-upgrade |
1 similar comment
/test pull-cluster-api-provider-azure-apiversion-upgrade |
@nawazkh: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
#5371 is the way to go ahead. So closing this PR for now. |
@nawazkh: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
10m
instead of1m
to see if that solves the upgrade issue.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 N/A
Special notes for your reviewer:
TODOs:
Release note: