-
Notifications
You must be signed in to change notification settings - Fork 430
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
Fix delete for VMSS flex #3256
Fix delete for VMSS flex #3256
Conversation
/test pull-cluster-api-provider-azure-e2e-optional |
/cherry-pick release-1.8 |
@CecileRobertMichon: once the present PR merges, I will cherry-pick it on top of release-1.8 in a new PR and assign it to you. 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/test-infra repository. |
/retest the flex MP failed to provision |
/retest e2e should be fixed now |
Sigh. |
/retest this time for real |
flex job failed (hasn't reported), but you can start investigating now @mboersma to see if this indeed didn't fix the issue: |
Um wut? I don't think that's part of the intended test, will fix. |
it's weird because the flex e2e test passed on my WIP PR for the same fix #3249 So either something changed since then or the autorest parse function isn't working as we expected |
/test pull-cluster-api-provider-azure-e2e-optional |
I've run this flex e2e spec locally, and tested scale in to 0 on Windows clusters manually through Tilt several times, for both Uniform and Flexible, and I don't see a problem. I think the issue was this PR referenced k8s v1.26.2 which has some Windows cloud-init issues in our reference image that we're working to fix (see kubernetes-sigs/image-builder#1109). I moved it back to v1.26.1. |
The
|
/retest |
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
/approve
The |
LGTM label has been added. Git tree hash: 7282a20cf4c44aad31cb9a3711d68c387df6d30c
|
[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 |
/retest |
/retest do we have an open flaky test issue for ClusterClass? |
I don't think so, but I'm repro'ing and investigating now and I'll add one. Edit: See #3313 |
@mboersma: 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/test-infra repository. I understand the commands that are listed here. |
@mboersma I think I have a pretty decent idea of root cause (see comments in #3313) and there are exact repros of the same error in main (https://storage.googleapis.com/kubernetes-jenkins/logs/periodic-cluster-api-provider-azure-e2e-main/1636248867903115264/artifacts/clusters/bootstrap/resources/capz-e2e-851wjq/KubeadmControlPlane/capz-e2e-851wjq-cc-rtlzw.yaml) so I'm tempted to override the optional test if the next run fails again /retest |
@CecileRobertMichon: new pull request created: #3314 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/test-infra repository. |
@CecileRobertMichon: new pull request created: #3315 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/test-infra repository. |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Fixes a bug parsing a VMSS Flex resourceID that led to problems scaling in a MachinePool. Also adds unit test cases that will fail if the code reverts and enables scaling down in the relevant e2e test.
Which issue(s) this PR fixes:
Fixes #3077
Special notes for your reviewer:
All credit goes to @CecileRobertMichon for tracking down the root cause of this issue. 🥇
TODOs:
Release note: