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
When using a single node vSAN cluster, clicking "Validate Config" on hcibench web ui, validation fails as tvm.ovf is configured to run as "vSAN Default Storage Policy". Changing this value to "Datastore Default" passes the test successfully as the VM inherits datastore properties.
Reproduction steps
Log into hcibench web interface, fill out fields, save and then validate config
Validate config fails as it expects to see two fault domains when I only have one
Modify /opt/output/vm-template/tvm/tvm.ovf so that "vSAN Default Storage Policy" becomes "Datastore Default" (optionally, changed description as well to match change)
Rerun validate config - tvm.ovf deploys successfully, test succeeds
...
This does not impact the ability to actually run fio VMs through the web ui as the script defaults to datastore default, and allows for manual storage policy declaration.
Expected behavior
While single node vSAN isn't supported in production, test VMs should still validate config as it is a valid vSphere configuration.
Additional context
Keep up the great work!
-vShoeString (vExpert)
The text was updated successfully, but these errors were encountered:
Describe the bug
When using a single node vSAN cluster, clicking "Validate Config" on hcibench web ui, validation fails as tvm.ovf is configured to run as "vSAN Default Storage Policy". Changing this value to "Datastore Default" passes the test successfully as the VM inherits datastore properties.
Reproduction steps
...
This does not impact the ability to actually run fio VMs through the web ui as the script defaults to datastore default, and allows for manual storage policy declaration.
Expected behavior
While single node vSAN isn't supported in production, test VMs should still validate config as it is a valid vSphere configuration.
Additional context
Keep up the great work!
-vShoeString (vExpert)
The text was updated successfully, but these errors were encountered: