-
Notifications
You must be signed in to change notification settings - Fork 127
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
Distributed-FIO: PV not getting mounted to server POD when created with pvcvolumemode: Block #793
Comments
How would a distributed fio work against a single block? Who'll coordinate the writes and reads? |
This issue came up when I was evaluating LVMO Block performance on SNO (by specifying VolumeMode = block in PVC). The FIO tests wouldn't run because of issue described above |
@mykaul - Ripsaw never shares the same PVC between Pods. Ripsaw creates as many Pods as we define in the |
@shekharberry I think you just need to fix this here: As far as I can see, fio on VMs should work fine already and is not affected by this bug |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Describe the bug
A clear and concise description of what the bug is.
When in distributed-FIO CR we specify pvcvolumemode: Block (Default is Filesystem), the PV is not getting mounted on the server POD. The PVC gets bound successfully.
The reason for this is for block mode the POD should have -devicePath but it has -mountPath. (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#pod-specification-adding-raw-block-device-path-in-container)
Here's the output of POD in yaml when pvcvolumemode is Block: http://pastebin.test.redhat.com/1067721
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
the pod yaml, should have something like this for block mode: (Note: its an example)
volumeDevices:
- devicePath: "/dev/xvda"
name: lvm-block-pvc
but it has
volumeDevices:
- mountPath: "/dev/xvda"
name: lvm-block-pvc
Note, for pvcvolumemode: Filesystem (Default Config), the server POD comes up and tests finish successfully.
The text was updated successfully, but these errors were encountered: