Refactor preparePVCDataSourceForProvisioning to support BlockVolume tests in multivolume.go #102787
Comments
@mauriciopoppe: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
@mauriciopoppe: The label(s) 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. |
@mauriciopoppe: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
Hey team! I'd like to further investigate on this issue if possible? |
/assign |
/area test hey @dbgoytia, sure, I've added more info about how to test it, it requires these components:
|
thanks a lot @mauriciopoppe !! I might be a bit slow though, I'm pretty new to the community. I appreciate the documentation you shared, the assignation and how to replicate it, I'll test it out and if I have some doubts, I'll get back with you :D |
What would you like to be added:
In #102775 block volume tests were skipped because
preparePVCDataSourceForProvisioning
is not usingutils.CheckWriteToPath / utils.CheckReadFromPath
, there are more details about how these functions are used inTestConcurrentAccessToSingleVolume
This is a test that uses the XFS, if tested using the GCE PD storage class it should have
fstype: xfs
, in addition the test cluster should have the VolumeSnapshot CRDs and the controllers installed/sig storage
/area testing
/good-first-issue
The text was updated successfully, but these errors were encountered: