Image provision (user_data): "Failed to create a compute... domain is required"

I've started working on provisioning a windows machine from a vsphere
template. I followed

tutorial, but I'm getting an error "We're sorry, but something went wrong".
I think that it has something to do with the user_data provision template
since using the steps from Deploying windows template from VSphere using theforeman | My Stuff I still can't
provision successfully, but this time another error is thrown "Failed to
create a compute… domain is required".

It might help if you provide more context including full messages and
logs from Foreman (production.log).

··· On 14/05/16 10:19, ghidu wrote: > I've started working on provisioning a windows machine from a vsphere > template. I followed > https://blog.inovex.de/deploying-windows-server-with-foreman-in-vsphere/ > tutorial, but I'm getting an error "We're sorry, but something went > wrong". I think that it has something to do with the user_data provision > template since using the steps from http://www.herbert.org.nz/?p=245 I > still can't provision successfully, but this time another error is > thrown "Failed to create a compute... domain is required".


Dominic Cleal
dominic@cleal.org

Thanks Dominic for the interest. I ended up setting up ssh for the Windows
image and attach a finish template to the OS.

··· On Monday, May 16, 2016 at 10:18:18 AM UTC+3, Dominic Cleal wrote: > > On 14/05/16 10:19, ghidu wrote: > > I've started working on provisioning a windows machine from a vsphere > > template. I followed > > https://blog.inovex.de/deploying-windows-server-with-foreman-in-vsphere/ > > tutorial, but I'm getting an error "We're sorry, but something went > > wrong". I think that it has something to do with the user_data provision > > template since using the steps from http://www.herbert.org.nz/?p=245 I > > still can't provision successfully, but this time another error is > > thrown "Failed to create a compute... domain is required". > > It might help if you provide more context including full messages and > logs from Foreman (production.log). > > -- > Dominic Cleal > dom...@cleal.org >