Or is there a way to tell winrm communicator to retry more times or set 
longer timeout somehow?

Keeping in mind that sysprep takes a while and also reboots the machine a 
couple of times...


On Friday, 22 July 2016 10:22:36 UTC-4, John Smith wrote:
>
> Hi can someone confirm if I can do this with the vagrant trigger plugin?
>
> I'm looking at the vagrant vSphere plugin and on action up 
>
>      def self.action_up
>        Vagrant::Action::Builder.new.tap do |b|
>          b.use HandleBox
>          b.use ConfigValidate
>          b.use ConnectVSphere
>          b.use Call, IsCreated do |env, b2|
>            if env[:result]
>              b2.use MessageAlreadyCreated
>              next
>            end
>
>             b2.use Clone
>          end
>          b.use Call, IsRunning do |env, b2|
>            b2.use PowerOn unless env[:result]
>          end
>          b.use CloseVSphere
>          b.use WaitForCommunicator
>          b.use Provision
>          b.use SyncedFolders
>          b.use SetHostname
>        end
>      end
>
>
> Is there a way to trigger on wait for communicator?
>
>
>
>
>
>
> On Wednesday, 20 July 2016 10:40:10 UTC-4, John Smith wrote:
>>
>> Ok so I'm trying the trigger plugin
>>
>>
>> This one works, it prints firing trigger before get state a few times
>>         config.trigger.before :ALL do
>>                 info "STATE!!!!"
>>         end
>>
>> This one doesn't work, nothing gets called
>>         config.trigger.before :state do
>>                 info "STATE!!!!"
>>         end
>>
>> This one doesn't work, nothing gets called
>>         config.trigger.before :boot do
>>                 info "BOOT!!!!"
>>         end
>>
>>
>>
>> On Wednesday, 20 July 2016 08:57:36 UTC-4, John Smith wrote:
>>>
>>> Cool I will try the trigger plugin. The cosequence is because of 
>>> sysprep. Basically you get that "Configuring windows for the first time" 
>>> screen which takes for ever and also causes windows to reboot.
>>
>>

-- 
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/eb667e8a-39c5-41fa-94b5-f4b127ac69cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to