hello, not sure if there is something natively, but maybe vagrant trigger can help, maybe running a sleep/wait on host after up, before script.
alvaro On Wed, Jul 20, 2016 at 2:39 PM, John Smith <[email protected]> wrote: > Hi, > > Using 1.8.4 > > I have created Vagrant file that launches a Windows VM using vCenter > Server with the provider plugin from NSIDC. It's all working fine and dandy > except that when Winrm tries to authenticate it happens before sysprep can > finish. > > Bringing machine 'default' up with 'vsphere' provider... > ==> default: Calling vSphere CloneVM with the following settings: > ==> default: -- Template VM: xxxxxx/vm/w2k8_r2_base_remoting > ==> default: -- Target VM: xxxxxx/vm/vagrant01 > ==> default: New virtual machine successfully cloned > default: WinRM address: xxx.xxx.xxx.xxx:5985 > ==> default: Waiting for machine to boot. This may take a few minutes... > default: WinRM username: xxxxxx <------- This section executes > immediately. Sysprep takes a while and also reboots a couple times... > default: WinRM execution_time_limit: PT2H > default: WinRM transport: negotiate > No route to host - connect(2) for "xxx.xxx.xxx.xxx" port 5985 > (xxx.xxx.xxx.xxx:5985) > > In vSphere client the machine created properly and is accessible with RDP > etc... > > If I run vagrant up again for the sake of it... > > Bringing machine 'default' up with 'vsphere' provider... > ==> default: The VM is already created > default: WinRM address: xxx.xxx.xxx.xxx:5985 > ==> default: Waiting for machine to boot. This may take a few minutes... > default: WinRM username: xxxxxx > default: WinRM execution_time_limit: PT2H > default: WinRM transport: negotiate > ==> default: Machine booted and ready! > > So is there a way to tell vagrant to wait before it tries to winrm? > > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/83cab438-b487-48d9-bc6c-266bdee2ae7e%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/83cab438-b487-48d9-bc6c-266bdee2ae7e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exXe8oE0drF0NzKKJoY9b9yZvfUry-subaACyovUVRYrA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
