You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Task drivers like QEMU can't support CSI, so we should show a useful error to the operator when they try to schedule a job (or validate one), rather than erroring-out at the client.
The text was updated successfully, but these errors were encountered:
I tested this out a bit and it looks like QEMU doesn't support host volumes either. But because there's no checking, the jobspec will let you configure it and it just won't work (the volume isn't mounted).
So I'm wondering whether we should add a new field to the Driver Capabilities struct so that we can test this as part of task driver fingerprinting. It would need to be backwards-compatible with existing fields, so maybe something like VolumeSupport as an enum that defaults to "all" but has a "host volumes only" (is that a thing?) and a "none" option.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Task drivers like QEMU can't support CSI, so we should show a useful error to the operator when they try to schedule a job (or validate one), rather than erroring-out at the client.
The text was updated successfully, but these errors were encountered: