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

Enable VAC tests #2220

Merged
merged 1 commit into from
Nov 8, 2024
Merged

Enable VAC tests #2220

merged 1 commit into from
Nov 8, 2024

Conversation

ElijahQuinones
Copy link
Member

What type of PR is this?

/kind cleanup

What is this PR about? / Why do we need it?

This PR enables VAC testing

How was this change tested?

CI

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Nov 8, 2024
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 8, 2024
Copy link

github-actions bot commented Nov 8, 2024

Code Coverage Diff

This PR does not change the code coverage

@torredil
Copy link
Member

torredil commented Nov 8, 2024

Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
...
InvalidParameterValue: The volume size is invalid for io2 volumes: 1 GiB. io2 volumes must be at least 4 GiB in size. Please specify a volume size above the minimum limit.

The size for volumes in external tests is defined here:

1Gi works for gp2/3, but is invalid for io2. Thoughts on modifying only iops or throughput as a path forward?

@ElijahQuinones
Copy link
Member Author

ElijahQuinones commented Nov 8, 2024

Using claimSize:1Gi, test suite supported size:{ 1Gi}, driver(ebs.csi.aws.com) supported size:{ 1Gi} 
...
InvalidParameterValue: The volume size is invalid for io2 volumes: 1 GiB. io2 volumes must be at least 4 GiB in size. Please specify a volume size above the minimum limit.

The size for volumes in external tests is defined here:

1Gi works for gp2/3, but is invalid for io2. Thoughts on modifying only iops or throughput as a path forward?

Seen this error as well when looking through logs addressed it by switching volume type to gp2

Also took out IOPS modification to not run into IOPS ratio errors.

1 handlers.go:76] "Error from AWS API" err="api error InvalidParameterCombination: Volumes greater than 16 TiB or 64K IOPS or 500:1 IOPS:GB ratio are only supported on instances compatible with io2 Block Express"
E1108 16:41:11.889161       1 driver.go:108] "GRPC error" err="rpc error: code = InvalidArgument desc = Could not modify volume (invalid argument) \"vol-0dfafacada6640c1e\": invalid argument: operation error EC2: ModifyVolume, https response error StatusCode: 400, RequestID: 8beff358-21b6-44cb-a0d3-adf27efcb9d2, api error InvalidParameterCombination: Volumes greater than 16 TiB or 64K IOPS or 500:1 IOPS:GB ratio are only supported on instances compatible with io2 Block Express"

If we would prefer though I can use gp3 and modify iops per gb to not run into this error if we want to test for more meaningful volume modifications.

@torredil
Copy link
Member

torredil commented Nov 8, 2024

That works well! @ElijahQuinones
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 8, 2024
@ConnorJC3
Copy link
Contributor

/approve

Type should be good for these tests, as we have things like iops in our own tests.

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ConnorJC3

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 8, 2024
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 8, 2024
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 8, 2024
@k8s-ci-robot k8s-ci-robot merged commit ef505ff into kubernetes-sigs:master Nov 8, 2024
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants