-
Notifications
You must be signed in to change notification settings - Fork 629
Remove suspend process flow from create ASG #3864
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
Remove suspend process flow from create ASG #3864
Conversation
/test ? |
@richardcase: The following commands are available to trigger required jobs:
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/test-infra repository. |
/test pull-cluster-api-provider-aws-e2e-eks |
I've been thinking about how to unit test this but it ain't an easy one. I was thinking about adding an e2e test but that takes time and I don't want to keep the upgrade test broken. @richardcase any ideas? |
I've toyed with the idea of adding the option to run "extended" e2e tests. |
It wouldn't be easy to unit test but it's doable. I can have a bash if you want? |
It's fine I'll be home soonish I'll take a stab at it. 😊 thank you. I'll shout if I get stuck. |
The question is what to unit test. I guess I can test that during an upgrade suspension is called while during create it does not. |
/test pull-cluster-api-provider-aws-e2e-eks |
Turns out I already head unit tests, but I was missing a call to the mock to verify that it is called or not. |
The previous eks failure was not because of this. The create ASG was successful:
|
Hmm, interesting. The test failed again. |
/test pull-cluster-api-provider-aws-e2e-eks |
Kind of suspicious. The Suspend PR had both these tests running:
And passing. |
I'm running eks test here as well #3804 Just to see if something isn't messed up. |
/test pull-cluster-api-provider-aws-e2e-eks |
/test pull-cluster-api-provider-aws-e2e-eks edit: Wohoo, this passed. |
/test pull-cluster-api-provider-aws-e2e-eks Once more into the fray. Once more we go. I want to see if AWS got their things together. :) |
/test pull-cluster-api-provider-aws-e2e-eks |
@richardcase @Ankitasw This is now ready. I don't think there is anything else to fix in here. Should I add a suspend e2e during this pr? |
It seems fine to push to v2.0.2 as it doesn't break any functionality and hence take care of E2E tests in a separate issue so: /lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ankitasw 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 |
/cherry-pick release-2.0 |
@Ankitasw: once the present PR merges, I will cherry-pick it on top of release-2.0 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. |
@Ankitasw: new pull request created: #3892 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. |
/kind bug
What this PR does / why we need it:
The suspend flow in the create ASG process is failing because during the ASG creation, we never return the actual ASG. That's because the CreateAutoscalingGroup flow is not returning an ASG so we reconcile it.
I just removed the suspend during creation, the update flow should still suspend or unsuspend anything that is different.
I'll try adding some more tests to this part of the code.
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:
Checklist: