-
Notifications
You must be signed in to change notification settings - Fork 174
DRS cluster doesn't detect default datastore and network #183
Comments
I just ran across this same issue. Any idea when it might get addressed? |
Specify the value explicitly. This issue is not so easy to fix. |
It's not just the VM host. It's a cycle. You add that, it asks for datastores, then when you add that it asks for networks, etc. Which means I have to build on one host which isn't the best option. |
Not sure I follow. On DRS-enabled clusters you don't need to specify |
We're running into this as well, but we do use a DRS enabled cluster, and we have specified both The issue seems to happen however upon uploading the floppy, not when creating the virtual machine itself. |
yes, I've reproduced the issue with floppy upload. As a workaround, you could try using the new |
@mkuzmin I see Version 2.2 is released with the Unfortunately the Tx - John |
Hmm - after talking with our Infra people, it looks like we don't have DRS enabled on our cluster anyway, so it may that the previous (2.1) release "worked" without specifying the host - so looking at a workaround on our side to determine a hostname to use for the build. |
I've fixed floppy upload and published a new release 2.3. |
@mkuzmin Thanks for the quick response on this. John |
I am using 2.3 and I have the same issues. Yet, I get the following error: If I force a host, then I get this new error: "Build 'vsphere-iso' errored: error creating vm: Host has multiple datastores. Specify it explicitly" In a cluster with DRS, both the host and datasource should be coming from the DRS. This is not the case. |
This appears related: #241 |
The first comment solves my error |
if
datastore
ornetwork
are not specified explicitly for DRS-enabled clusters, then a build fails withThe text was updated successfully, but these errors were encountered: