Skip to content
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

Another reduction of describe via reducing the number of list calls #4772

Merged
merged 3 commits into from
Feb 14, 2022
Merged

Another reduction of describe via reducing the number of list calls #4772

merged 3 commits into from
Feb 14, 2022

Conversation

Skarlso
Copy link
Contributor

@Skarlso Skarlso commented Feb 10, 2022

Part 2 Of refactoring GetStackTemplate and DescribeStack

This time, Describe is reduced due to the number of reduced list calls during deletion. It's possible to pass around stacks by adding Stack to the nodeGroupStack and reducing the number of calls by moving around lists which already happened at the top level.

Related to: #4635

Integration Test Run results

Ran 43 of 43 Specs in 4572.260 seconds
FAIL! -- 41 Passed | 2 Failed | 0 Pending | 0 Skipped
--- FAIL: TestCRUD (4572.28s)

The 2 failures appear to be unrelated, but I'll make sure.

Nodegroup tests incoming...

Hmmm.... Node listing works by hand, but this test keeps failing which makes me think either the test is missing something that I need to add, or I'm missing something from somewhere. The code should work fine, this is just listing. Basically get nodegroups fails but it makes no sense why.

Managed Nodegroup test:

/Users/skarlso/goprojects/weaveworks/eksctl/integration/tests/managed/managed_nodegroup_test.go:441

Ran 21 of 21 Specs in 4950.664 seconds
FAIL! -- 20 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestManaged (4950.67s)

Fixed the failure and rerun the failing part:

failed...
Error: upgrade is only supported for managed nodegroups; could not find one with name "bottlerocket-1"

This is definitely a problem somewhere ^^. I run it isolation so it didn't create that nodegroup 🤦.
But it's fine, because upgradeNg(initialAl2Nodegroup) this passed so the other one should have as well.

Just going to run the integration test suit on my branch -> https://github.com/weaveworks/eksctl-ci/actions/runs/1830405203

@Skarlso Skarlso added the kind/feature New feature or request label Feb 10, 2022
@@ -50,10 +50,6 @@ func (c *OwnedCluster) Upgrade(dryRun bool) error {
return err
}

if err := c.ctl.RefreshClusterStatus(c.cfg); err != nil {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was redundant as New already called this.

@Skarlso
Copy link
Contributor Author

Skarlso commented Feb 11, 2022

I don't see how my changes here could affect Get.

aclevername
aclevername previously approved these changes Feb 11, 2022
Copy link
Contributor

@aclevername aclevername left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@Skarlso Skarlso dismissed aclevername’s stale review February 11, 2022 12:36

I pushed in some more changes, sorry :/

@Skarlso
Copy link
Contributor Author

Skarlso commented Feb 12, 2022

Integration tests passed on this Branch. ( I pushed it to eksctl directly too with the current change set.)

@Skarlso Skarlso enabled auto-merge (squash) February 14, 2022 07:28
@Skarlso Skarlso merged commit fb2c6ee into eksctl-io:main Feb 14, 2022
@hspencer77 hspencer77 mentioned this pull request Jul 8, 2022
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants