-
Notifications
You must be signed in to change notification settings - Fork 795
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
Improve observability of InsufficientVolumeCapacity
errors
#2155
Conversation
Signed-off-by: torredil <torredil@amazon.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Code Coverage DiffThis PR does not change the code coverage |
/retest |
AvailabilityZone: expZone, | ||
}, | ||
expCreateVolumeInput: &ec2.CreateVolumeInput{ | ||
Iops: aws.Int32(2000), |
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.
Is there a reason we need this iops input?
@torredil: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
@@ -176,6 +176,9 @@ var ( | |||
|
|||
// ErrInvalidRequest is returned if parameters were rejected by driver | |||
ErrInvalidRequest = errors.New("invalid request") | |||
|
|||
// ErrInsufficientVolumeCapacity is returned when there's not enough capacity to fulfill the volume provision request. | |||
ErrInsufficientVolumeCapacity = errors.New("There is not enough capacity to fulfill your EBS volume provision request. You can try to provision a different volume type, EBS volume in a different availability zone, or you can wait for additional capacity to become available.") |
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.
Why are we adding our own error message here? Is the error message from EBS not sufficient?
(What even is the error message the EBS API returns here? Neither the PR nor the linked issue contains it)
/close |
@torredil: Closed this PR. 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-sigs/prow repository. |
Is this a bug fix or adding new feature?
Neither, kaizen.
closes #2154
What is this PR about? / Why do we need it?
This PR enhances the driver's ability to communicate
InsufficientVolumeCapacity
errors from the AWS API by providing a more informative error message to users.What testing is done?
See https://docs.aws.amazon.com/AWSEC2/latest/APIReference/errors-overview.html for more information related to error codes.