Epic Goal*

Add a new test to upstream csi-test repo that checks a CSI driver increases volume size to the nearest volume size supported by the driver.

Why is this important? (mandatory)

csi-tests is an unit/integration test suite used by some CSI driver vendors and having such a test there could prevent them from hitting issues in OCP / CNV:

CNV / KubeVirt needs to provision a relatively small volume (hundreds of MB) and expect that CSI driver rounds it up to a nearest supported volume size (say to 4 GiB for AWS EBS io2 volume). This is also requirement from the CSI spec. Users / CNV then don't need to figure out what volume sizes the CSI driver supports and can remove driver specific code.

We don't use these tests in OCP, this is pure upstream contribution.

Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. As CSI driver vendor, I can run csi-tests and be sure that my rounding is correct.

 
Dependencies (internal and external) (mandatory)

None

Contributing Teams(and contacts) (mandatory) 

• Development

Acceptance Criteria (optional)

The test is implemented in csi-tests repo.

Drawbacks or Risk (optional)

Done - Checklist (mandatory)