-
Notifications
You must be signed in to change notification settings - Fork 808
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 volume/snapshot tagging and FSR e2e tests #1847
Conversation
Code Coverage DiffThis PR does not change the code coverage |
caf5951
to
11c2f04
Compare
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.
Great work and thanks for all the added test-coverage gained by integrating EC2 API into our e2e tests. I might integrate EC2 API into ModifyVolume e2e tests now too.
Here are a few comments after my first look, might have a few more comments after we merge the refactoring PR that this is stacked on top of.
tests/e2e/requires_aws_api.go
Outdated
}, | ||
ClaimSize: driver.MinimumSizeForVolumeType(awscloud.VolumeTypeGP3), | ||
VolumeMount: testsuites.VolumeMountDetails{ | ||
NameGenerate: "test-volume-", |
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.
Let's rely on DefaultVolumeName and DefaultMountPath for these test's VolumeMount's? (Or create a VolumeMount const in e2e_utils shared across each test-case?)
(To not have hanging constants. Yes, the old dynamic provisioning tests would need to be refactored to use these as well, but I think that's a PR worth making.)
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.
I don't using those defaults is reasonable because this is a generator so those values don't make sense. I created a DefaultGeneratedVolumeMount
var (cannot be const, as its a struct) instead.
PR needs rebase. 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. |
11c2f04
to
45e5fd1
Compare
…verwriting existing with nil Signed-off-by: Connor Catlett <conncatl@amazon.com>
45e5fd1
to
46a2f03
Compare
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 |
/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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ConnorJC3, torredil 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 |
Is this a bug fix or adding new feature?
New feature for e2e tests
What is this PR about? / Why do we need it?
This PR is split into 3 commits:
Fixes a minor logging bug discovered during the e2e test development
Adds tests for creating a volume and snapshot with additional tags
Adds tests for creating a snapshot with an FSR zone
What testing is done?
This PR is adding new tests