kubernetes: storage e2e: make read-only block optional
Which jobs are failing:
vsphere CSI
Which test(s) are failing:
CSI Volumes [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should concurrently access the single read-only volume from pods on the same node
Since when has it been failing:
since the test was introduced
Testgrid link:
n/a
Reason for failure:
FailedMapVolume: MapVolume.MapPodDevice failed for volume "pvc-5ccaf85d-af04-4c7f-a2b6-aeb239f33e96" : rpc error: code = InvalidArgument desc = read only not supported for Block Volume
Anything else we need to know:
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 24 (13 by maintainers)
This test tries to set pod.volumes.readonly in block mode which I think most volume plugins don’t support. I think read-only block can only be enforced at attach-level, not node stage/publish level.
I double checked pd csi implementation to see why the test is passing there, and it’s not enforcing/checking, but it probably should since the device ends up writable to the pod. cc @mattcary
@jsafrane do you think it makes sense to make this test case a plugin capability?
@kubernetes/sig-storage-test-failures