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

Add e2e test for upgrading management-components #7251

Merged
merged 1 commit into from
Jan 5, 2024

Conversation

d8660091
Copy link
Member

@d8660091 d8660091 commented Jan 4, 2024

Issue #, if available:

Description of changes:

Testing (if applicable): Manually invoked the new e2e test, and it passed.

Documentation added/planned (if applicable):

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@eks-distro-bot eks-distro-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jan 4, 2024
Copy link

codecov bot commented Jan 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ec9bd81) 71.63% compared to head (40b4bc0) 71.64%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7251   +/-   ##
=======================================
  Coverage   71.63%   71.64%           
=======================================
  Files         556      556           
  Lines       43199    43199           
=======================================
+ Hits        30945    30948    +3     
+ Misses      10543    10541    -2     
+ Partials     1711     1710    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@d8660091 d8660091 changed the title Add e2e test for upgrading management-components [WIP] Add e2e test for upgrading management-components Jan 4, 2024
@d8660091 d8660091 force-pushed the e2e-upgrade-management-components-2 branch from a8fccd1 to 7453ba6 Compare January 4, 2024 18:30
@d8660091 d8660091 force-pushed the e2e-upgrade-management-components-2 branch from 7453ba6 to 40b4bc0 Compare January 4, 2024 18:54
@d8660091 d8660091 changed the title [WIP] Add e2e test for upgrading management-components Add e2e test for upgrading management-components Jan 4, 2024
// create cluster with old eksa
test.CreateCluster(framework.ExecuteWithEksaRelease(release))
// upgrade management-components with new eksa
test.RunEKSA([]string{"upgrade", "management-components", "-f", test.ClusterConfigLocation, "-v", "99"})
Copy link
Member

Choose a reason for hiding this comment

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

nit: I think that we should we create a test.UpgradeManagmentComponents function and hide these details.

Copy link
Member

@cxbrowne1207 cxbrowne1207 left a comment

Choose a reason for hiding this comment

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

Do we also need this to test completing the rest of the upgrade after running upgrade management components?

@d8660091
Copy link
Member Author

d8660091 commented Jan 5, 2024

Do we also need this to test completing the rest of the upgrade after running upgrade management components?

Because the followup procedure of upgrading the cluster itself will fail due to the bug: https://github.com/aws/eks-anywhere-internal/issues/2126. And I think right now we need a test case to cover the most essential flow of the new subcommand more than we need a comprehensive one that verify the flow of eksa controller reconciliation process. Having said that, we can do this in another PR when the bug is fixed

@cxbrowne1207
Copy link
Member

/lgtm

@d8660091
Copy link
Member Author

d8660091 commented Jan 5, 2024

/approve

@eks-distro-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: d8660091

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@d8660091 d8660091 merged commit 7c8b62f into aws:main Jan 5, 2024
9 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants