-
Notifications
You must be signed in to change notification settings - Fork 431
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 CAPI to v0.4.3 #1728
Update CAPI to v0.4.3 #1728
Conversation
/test pull-cluster-api-provider-azure-capi-e2e |
/retest |
/test pull-cluster-api-provider-azure-e2e |
/test pull-cluster-api-provider-azure-test |
looks like cluster pause/unpause tests are failing this is the second failure in a row, I think this is an actual failure |
/test pull-cluster-api-provider-azure-coverage |
5dfc2ad
to
35cfc21
Compare
@@ -48,7 +48,7 @@ func GenerateCreateNotPausedLogEntries(ec EntryCriteria) []gomega.LogMatcher { | |||
ec.ClusterName, | |||
"msg", | |||
"Cluster is not paused, allowing further processing", | |||
).WithLevel(4).WithLogFunc("Info") | |||
).WithLevel(6).WithLogFunc("Info") |
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.
35cfc21
to
76853c9
Compare
/retest |
/test pull-cluster-api-provider-azure-capi-e2e |
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.
/lgtm
/test pull-cluster-api-provider-azure-e2e-exp |
/test pull-cluster-api-provider-azure-capi-e2e |
/approve |
/hold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
the same test failed again with what seems to be connection timeout to the apiserver. The same test seems stable on main: https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-azure#capz-periodic-capi-e2e-main trying again in case we got unlucky twice /retest |
seeing consistent errors when deleting resource group https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-azure/1728/pull-cluster-api-provider-azure-capi-e2e/1442612992054136832/artifacts/clusters/bootstrap/controllers/capz-controller-manager/capz-controller-manager-67bfdf96f9-9txc2/manager.log |
The log above is expected, it just means the RG was not done deleting yet (it takes a while). The real error on that test was
which is different from the MHC error we got previously. /retest |
/hold cancel |
What type of PR is this?
What this PR does / why we need it: https://github.com/kubernetes-sigs/cluster-api/releases/tag/v0.4.3
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:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: