-
Notifications
You must be signed in to change notification settings - Fork 29
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
Bug 1870489: Verify that tests correctly handle not rounding to the GiB #64
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: derek-pryor 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 |
@derek-pryor: This pull request references Bugzilla bug 1870489, which is invalid:
Comment 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/test-infra repository. |
/assign @jsafrane |
/hold |
@derek-pryor: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
I can see that the CSI driver got most of the CreateVolume requests call asking for 100MiB (=104857600 bytes) volume:
In the same log file I can see four requests for 1GiB (1073741824 bytes):
I can see ControllerExpandVolume was called on each of them (in the other driver log file), hence I deduct that these are volume expansion tests that use 1GiB as their minimal volume size for testing. We can conclude that today's external-provisioner does not round volumes to 1GiB and there is nothing to fix. |
Closing as verification was successful. |
Verify that PR #199 addresses Issue #94128 by changing the vSphere tests to use a non GiB aligned minimum value. The vSphere CSI driver is used because it is one of the few drivers that doesn't round to the GiB.