As at Vagrant 1.9.1 the reboot during provisioning is successful around 75% of the time. I believe that if the host is performing well, the reboot will execute within the Vagrant reconnect maximum and the provisioning will proceed. I've seen two different strategies from other users (see links above) where the DC promotion is attempted with reboot disabled and the other attempts to insert a sleep. I suspect these may have worked in previous versions of Vagrant consistently fail in 1.9.1. Because the reconnect works most of the time, I'm confident an increase in the number of retries would overcome this occasional failure.
On Thursday, January 19, 2017 at 8:47:39 AM UTC+13, Alvaro Miranda Aguilera wrote: > Hello > > On windows, is normal practice to schedule the scripts to run with the > task schduler. Say to start in 1 minute from now. > > then vagrant will stop the provisioning and 1 min later the DC > promotion/reboot will happen. > > If your script keep the session open and reboot/disconnect, vagrant will > fail as you have found. > > I am not aware of vagrant being able to handle reboots in/between script > provision. > > Alvaro > > On Wed, Jan 18, 2017 at 7:55 PM, Jules & Amy Clements <[email protected] > <javascript:>> wrote: > >> Even with an extremely high limit, it is still failing, I'm not convinced >> this setting even does anything. >> >> override.winrm.retry_limit = 200 >> >> rescue in block in parse_header': HTTPClient::KeepAliveDisconnected >> >>> >>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/386b2ff7-cad0-4be7-9a97-c88b7d36e649%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/386b2ff7-cad0-4be7-9a97-c88b7d36e649%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > > -- 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/44a0d723-0ad5-4ab3-9827-cfb94d6ea81a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
